From: Lauri Alanko <la@iki.fi>
To: caml-list@inria.fr
Subject: [Caml-list] Capitalized source file names
Date: Sun, 26 Dec 2010 22:37:11 +0200 [thread overview]
Message-ID: <20101226203711.GA10137@melkinpaasi.cs.helsinki.fi> (raw)
Traditionally, OCaml source files have been named to start with
lowercase letters, even though they define modules whose names begin
with uppercase letters: the definition of module FooBar goes in
fooBar.ml. This has always seemed unintuitive to me.
I'm not sure if this convention has been forced in the past, but
nowadays the entire toolchain seems to support capitalized filenames:
you can put the definition of FooBar in FooBar.ml, and everything just
works. This seems much more natural.
As things stand, is there any reason (besides uniformity with existing
code) why one shouldn't use capitalized source file names nowadays?
Lauri
next reply other threads:[~2010-12-26 20:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-26 20:37 Lauri Alanko [this message]
2010-12-26 21:09 ` Philippe Wang
2010-12-27 9:44 ` David Allsopp
2010-12-26 21:26 ` Lukasz Stafiniak
2010-12-27 9:44 ` David Allsopp
2010-12-30 12:52 ` Florent Ouchet
2010-12-26 23:21 ` [Caml-list] " Sylvain Le Gall
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=20101226203711.GA10137@melkinpaasi.cs.helsinki.fi \
--to=la@iki.fi \
--cc=caml-list@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).