caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Junsong Li <ljs.darkfish@gmail.com>
To: Gabriel Scherer <gabriel.scherer@gmail.com>
Cc: Jeremie Dimino <jdimino@janestreet.com>, caml users <caml-list@inria.fr>
Subject: Re: [Caml-list] Can we implement #load to load dependencies automatically?
Date: Fri, 29 Apr 2016 18:54:41 -0700	[thread overview]
Message-ID: <CA+kGxtOLtaYzyzZsLJZ2r-vDrpZ_KoXVyMWsD5g1HSqab0OKwg@mail.gmail.com> (raw)
In-Reply-To: <CAPFanBFw3nCDcMuivVPjQsKcxKsTKbCyY75KGj69v=mrPz3CKg@mail.gmail.com>

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

Oops, I need to read the manual more carefully. #load_rec works.

Thanks!

On Fri, Apr 29, 2016 at 3:54 AM, Gabriel Scherer <gabriel.scherer@gmail.com>
wrote:

> Note that since 4.03, the OCaml toplevel comes with a "#help"
> directive that makes it easy to discover the available directives
> and their meaning.
>
> Utop, even on earlier OCaml versions, additionally provides an
> #utop_help command that describes utop-specific features (key
> bindings, macros).
>
> On Fri, Apr 29, 2016 at 6:28 AM, Jeremie Dimino <jdimino@janestreet.com>
> wrote:
> > If all dependencies are in the search path, you should be able to use
> > `#load_rec`, which does exactly this
> >
> > On Fri, Apr 29, 2016 at 5:57 AM, Junsong Li <ljs.darkfish@gmail.com>
> wrote:
> >>
> >> Hi list,
> >>
> >> I am wondering why we can't make #load to load everything needed
> >> automatically, given object files already in the search path.
> >>
> >> FYI, currently, it only shows the error (t opens B and uses B.x)
> >>
> >> utop # #load "t.cmo";;
> >> Error: Reference to undefined global `B'
> >
> >
> >
> >
> > --
> > Jeremie
>

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

      reply	other threads:[~2016-04-30  1:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-29  4:57 Junsong Li
2016-04-29 10:28 ` Jeremie Dimino
2016-04-29 10:54   ` Gabriel Scherer
2016-04-30  1:54     ` Junsong Li [this message]

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=CA+kGxtOLtaYzyzZsLJZ2r-vDrpZ_KoXVyMWsD5g1HSqab0OKwg@mail.gmail.com \
    --to=ljs.darkfish@gmail.com \
    --cc=caml-list@inria.fr \
    --cc=gabriel.scherer@gmail.com \
    --cc=jdimino@janestreet.com \
    /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).