From: "Nicolas Pouillard" <nicolas.pouillard@gmail.com>
To: "Joel Reymont" <joelr1@gmail.com>
Cc: "Caml List" <caml-list@inria.fr>
Subject: Re: [Caml-list] ocamldep and CamelCased.ml
Date: Tue, 1 May 2007 09:28:21 +0200 [thread overview]
Message-ID: <cd67f63a0705010028g61a54222ye6ac6927047a484b@mail.gmail.com> (raw)
In-Reply-To: <E0BF4C18-5E8F-484F-87E6-1C5DF12B602C@gmail.com>
On 5/1/07, Joel Reymont <joelr1@gmail.com> wrote:
> I noticed that ocamldep can't process Test.ml, etc. in 3.10. I also
> noticed that camlp4 uses camel-cased file names exclusively. How does
> ocamldep work with camlp4 then?
>
ocamldep works fine on CamelCase file names.
--
Nicolas Pouillard
next prev parent reply other threads:[~2007-05-01 7:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-30 22:16 Joel Reymont
2007-05-01 7:28 ` Nicolas Pouillard [this message]
2007-05-01 8:28 ` [Caml-list] " Joel Reymont
[not found] <20070501100005.52F7DBC76@yquem.inria.fr>
2007-05-01 13:36 ` David Allsopp
2007-05-01 13:43 ` Joel Reymont
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=cd67f63a0705010028g61a54222ye6ac6927047a484b@mail.gmail.com \
--to=nicolas.pouillard@gmail.com \
--cc=caml-list@inria.fr \
--cc=joelr1@gmail.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).