From: Xavier Leroy <Xavier.Leroy@inria.fr>
To: Donald Syme <Donald.Syme@cl.cam.ac.uk>, fbesnard <fbesnard@ac-nice.fr>
Cc: "'caml-list@inria.fr'" <caml-list@inria.fr>
Subject: Re: per-line comments
Date: Mon, 22 Jun 1998 10:51:17 +0200 [thread overview]
Message-ID: <19980622105117.39832@pauillac.inria.fr> (raw)
In-Reply-To: <E0ymU5G-000632-00@heaton.cl.cam.ac.uk>; from Donald Syme on Thu, Jun 18, 1998 at 03:05:29AM +0100
> > - there is no 'per line' comment (like Ada's "--" or C++'s "//" ) ?
> I too think this is a must. It may not quite accord with the personal
> tastes of the CaML implementors,
Caml's comment syntax is more a question of historical tradition than
personal tastes. After all, the comment syntax is perhaps the only
bit of syntax that hasn't changed between LCF ML, Caml, and Standard ML...
> but many good programmers use this
> extensively in their in-line documentation.
I don't quite get the point about in-line documentation. I write
perfectly fine on-line documentation between (* and *). Why would it
be any better with // or -- ?
> I figure they should be
> able to transfer their "existing practice" when they make the switch to
> CaML, just to make the switch as painless as possible.
Depends from which background you come. E.g. for a well-trained C
programmer, delimited comments make more sense.
At any rate, the main problem with per-line comments (as with most
syntax extension) is that they need a reserved symbol. Both // and --
are valid OCaml infix identifiers; // is even used in the Num standard
library module.
- Xavier Leroy
next prev parent reply other threads:[~1998-06-23 0:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-06-17 13:17 are initial values in class fields mandatory ? (ocaml) fbesnard
1998-06-18 2:05 ` Donald Syme
1998-06-22 8:51 ` Xavier Leroy [this message]
1998-06-23 0:24 ` per-line comments Pierre Weis
1998-06-18 6:40 ` are initial values in class fields mandatory ? (ocaml) Francois Pessaux
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=19980622105117.39832@pauillac.inria.fr \
--to=xavier.leroy@inria.fr \
--cc=Donald.Syme@cl.cam.ac.uk \
--cc=caml-list@inria.fr \
--cc=fbesnard@ac-nice.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