caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Philippe Veber <philippe.veber@gmail.com>
To: David Sheets <sheets@alum.mit.edu>
Cc: caml users <caml-list@inria.fr>
Subject: Re: [Caml-list] Fwd: Toplevel and syntax extension.
Date: Tue, 1 Jul 2014 19:06:04 +0200	[thread overview]
Message-ID: <CAOOOohRO3o0D8RW2jSAZ5gYrV-cDw4VpN-U3k-5JYv8dZm+-Vw@mail.gmail.com> (raw)
In-Reply-To: <CAAWM5TyC4ti6TWLCJt961bOiMAx5610VQ9cyo632hJNJPE9aQg@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1795 bytes --]

Thanks David!

The first call fails with a syntax error on "with sexp":

[pbil:~ 18:58]$cat rien.ml
let () =
  try Topdirs.dir_directory (Sys.getenv "OCAML_TOPLEVEL_PATH")
  with Not_found -> ()
;;

#use "topfind";;
#camlp4o;;
#require " sexplib.syntax";;

open Sexplib.Std;;

type t = int with sexp;;

[pbil:~ 18:58]$ocaml rien.ml
File "rien.ml", line 12, characters 13-17:
Error: Syntax error

It seems like the sexp syntax extension is not loaded when the script is
evaluated. But it's not really clear to me what going wrong...

Cheers!
ph.



2014-07-01 18:51 GMT+02:00 David Sheets <sheets@alum.mit.edu>:

> On Tue, Jul 1, 2014 at 5:38 PM, Philippe Veber <philippe.veber@gmail.com>
> wrote:
> > Reposting this question here, just in case.
> >
> > ---------- Forwarded message ----------
> > From: Philippe Veber <philippe.veber@gmail.com>
> > Date: 2014-06-28 21:32 GMT+02:00
> > Subject: Toplevel and syntax extension.
> > To: ocaml_beginners@yahoogroups.com
> >
> >
> > Dear camlers,
> >
> > Consider the following script:
> >
> > #use "topfind";;
> > #camlp4o;;
> > #require "sexplib.syntax";;
> >
> > open Sexplib.Std;;
> >
> > type t = int with sexp;;
> >
> > Saved as script.ml, the simple call:
> >
> > ocaml script.ml
> >
> > fails while the call:
> >
> > cat script.ml | ocaml
> >
> > succeeds. Any idea how I could fix the first call?
>
> How does the first call fail? A difference between the two is that, in
> the second, the .ocamlinit file is used. If you are using opam with
> ocamlfind installed via it, this file will contain your Topdirs setup.
> You can try:
>
> let () =
>   try Topdirs.dir_directory (Sys.getenv "OCAML_TOPLEVEL_PATH")
>   with Not_found -> ()
> ;;
>
> at the top of your script (after hashbang but before directives).
>
> Hope this helps,
>
> David
>

[-- Attachment #2: Type: text/html, Size: 3016 bytes --]

  reply	other threads:[~2014-07-01 17:06 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAOOOohTxesz1QpzFYO5RvjwpwRbuRJ_wKvYsYOqb23FsYKDVQg@mail.gmail.com>
2014-07-01 16:38 ` Philippe Veber
2014-07-01 16:51   ` David Sheets
2014-07-01 17:06     ` Philippe Veber [this message]
2014-07-02  8:08       ` Fabrice Le Fessant
2014-07-02 11:48         ` Philippe Veber
2014-07-02 12:01           ` Romain Bardou
2014-07-02 14:48             ` Philippe Veber
2014-07-02 15:20               ` Ashish Agarwal
2014-07-03  6:16                 ` Philippe Veber
2014-07-02 12:51           ` Fabrice Le Fessant
2014-07-02 14:46             ` Philippe Veber

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAOOOohRO3o0D8RW2jSAZ5gYrV-cDw4VpN-U3k-5JYv8dZm+-Vw@mail.gmail.com \
    --to=philippe.veber@gmail.com \
    --cc=caml-list@inria.fr \
    --cc=sheets@alum.mit.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).