From: Lukasz Stafiniak <lukstafi@gmail.com>
To: Lauri Alanko <la@iki.fi>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] Capitalized source file names
Date: Sun, 26 Dec 2010 22:26:14 +0100 [thread overview]
Message-ID: <AANLkTi=+5Jtm4LbvQ0O+RzCWViGNwWrg8+24_BQaOXoP@mail.gmail.com> (raw)
In-Reply-To: <20101226203711.GA10137@melkinpaasi.cs.helsinki.fi>
On Sun, Dec 26, 2010 at 9:37 PM, Lauri Alanko <la@iki.fi> wrote:
>
> As things stand, is there any reason (besides uniformity with existing
> code) why one shouldn't use capitalized source file names nowadays?
>
Last time I checked, the (native code ocaml) debugger was not working
properly with uppercase file names. But I haven't used the debugger in
a looong while (it's easier to use "printf"s).
Happy New Year.
next prev parent reply other threads:[~2010-12-26 21:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-26 20:37 Lauri Alanko
2010-12-26 21:09 ` Philippe Wang
2010-12-27 9:44 ` David Allsopp
2010-12-26 21:26 ` Lukasz Stafiniak [this message]
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='AANLkTi=+5Jtm4LbvQ0O+RzCWViGNwWrg8+24_BQaOXoP@mail.gmail.com' \
--to=lukstafi@gmail.com \
--cc=caml-list@inria.fr \
--cc=la@iki.fi \
/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