From: "Daniel Bünzli" <daniel.buenzli@erratique.ch>
To: caml-list caml-list <caml-list@yquem.inria.fr>
Subject: Re: [Caml-list] Working on dependent projects with ocamlbuild
Date: Thu, 1 Nov 2007 13:51:15 +0100 [thread overview]
Message-ID: <DE07F5D1-7B0E-412B-A5BB-E445DF18B863@erratique.ch> (raw)
In-Reply-To: <12B29D95-87FB-43F1-A26F-6128EB41FDF5@erratique.ch>
Le 1 nov. 07 à 11:53, Daniel Bünzli a écrit :
> The base project is structured as follows :
>
> base/src/a.ml
> base/src/b.ml
> base/src/base.ml
> base/src/base.mli
Actually, if the emacs mode had a code-folding mode (module folding
to be precise) I'd seriously consider the option of writing all the
code in base.ml. Which would solve my problem while retaining the
convenience of the initial symlink solution.
Daniel
next prev parent reply other threads:[~2007-11-01 12:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-24 11:07 Daniel Bünzli
2007-10-24 12:10 ` [Caml-list] " Matthieu Dubuget
2007-10-24 13:09 ` Nicolas Pouillard
2007-11-01 10:53 ` Daniel Bünzli
2007-11-01 12:51 ` Daniel Bünzli [this message]
2007-11-02 15:32 ` Nicolas Pouillard
2007-11-04 21:08 ` Daniel Bünzli
2007-11-05 10:02 ` Nicolas Pouillard
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=DE07F5D1-7B0E-412B-A5BB-E445DF18B863@erratique.ch \
--to=daniel.buenzli@erratique.ch \
--cc=caml-list@yquem.inria.fr \
/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).