From: Damien Doligez <damien.doligez@inria.fr>
To: OCaml <caml-list@inria.fr>
Subject: Re: [Caml-list] emacs mode?
Date: Fri, 28 Jan 2011 15:26:49 +0100 [thread overview]
Message-ID: <5CB1414F-852E-4B33-95D3-FE80A9ACAEDF@inria.fr> (raw)
In-Reply-To: <AANLkTimLenarWQ71J+J6C+MC2amdWiiMkCyTsvE7rVUm@mail.gmail.com>
On 2011-01-27, at 21:27, Ashish Agarwal wrote:
> The double semicolon is mostly used in the top-level. Although there is sometimes good use of them in source files, it is bad style to include them unnecessarily.
Style is subjective, but note that the double semicolons make it much
easier for random tools (including the compiler) to find out where your
phrases begin and end.
It also makes it easier to copy your code and paste it to the toplevel.
-- Damien
next prev parent reply other threads:[~2011-01-28 14:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-26 23:47 Raoul Duke
2011-01-27 13:38 ` Daniel Bünzli
2011-01-27 15:08 ` Ashish Agarwal
2011-01-27 18:46 ` Raoul Duke
2011-01-27 20:27 ` Ashish Agarwal
2011-01-27 20:29 ` Raoul Duke
2011-01-28 14:26 ` Damien Doligez [this message]
2011-01-27 20:09 ` Lukasz Stafiniak
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=5CB1414F-852E-4B33-95D3-FE80A9ACAEDF@inria.fr \
--to=damien.doligez@inria.fr \
--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