From: Michal Moskal <malekith@pld-linux.org>
To: Brian Hurt <brian.hurt@qlogic.com>
Cc: Basile STARYNKEVITCH <basile@starynkevitch.net>, caml-list@inria.fr
Subject: Re: [Caml-list] single-line comment request
Date: Tue, 8 Apr 2003 23:37:35 +0200 [thread overview]
Message-ID: <20030408213735.GA3061@roke.freak> (raw)
In-Reply-To: <Pine.LNX.4.33.0304081518350.2225-100000@eagle.ancor.com>
On Tue, Apr 08, 2003 at 03:22:59PM -0500, Brian Hurt wrote:
> On Tue, 8 Apr 2003, Basile STARYNKEVITCH wrote:
>
> > I also suggest the following di-graph for comments
> > #! (which is compatible with Unix first line execve convention)
>
> Aha! OK- here is a really good reason to add single line comments, with
> #! as the comment delimiter- so we can put
> #!/usr/local/bin/ocaml
> as the first line in our programs, and have Ocaml as an interpreted
> scripting language, as well as a interpreter/bytecode/native language.
ocaml (as opposed to ocamlc) recognizes this as comment, but only at the
first line of a file.
> All of the above are valid operator names. Not sure about [*]. See page
> 91 of the language standard.
Neither [*] nor #! are accepted by ocamlc as operator names.
I personally would find single line comments useful for turning various
debugging (single line) calls on/off, e.g.:
f ();
(* dbg "f done"; *)
let i = g () in
dbg "g done, %d" i;
h ()
But I don't care much, just need to write vim macro :-)
--
: Michal Moskal :: http://www.kernel.pl/~malekith : GCS {C,UL}++++$ a? !tv
: PLD Linux ::::::::: Wroclaw University, CS Dept : {E-,w}-- {b++,e}>+++ h
-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
next prev parent reply other threads:[~2003-04-08 21:39 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-08 12:56 Nickolay Semyonov-Kolchin
2003-04-08 15:17 ` Samuel Lacas
2003-04-08 14:27 ` Nickolay Semyonov-Kolchin
2003-04-08 16:21 ` Samuel Lacas
2003-04-09 15:15 ` Thierry SALSET
2003-04-08 15:19 ` Brian Hurt
2003-04-08 14:25 ` Nickolay Semyonov-Kolchin
2003-04-08 16:08 ` Brian Hurt
2003-04-08 15:38 ` Nickolay Semyonov-Kolchin
2003-04-08 17:42 ` Brian Hurt
2003-04-08 17:31 ` Chris Hecker
2003-04-08 16:29 ` Nickolay Semyonov-Kolchin
2003-04-08 19:26 ` Basile STARYNKEVITCH
2003-04-08 20:22 ` Brian Hurt
2003-04-08 21:37 ` Michal Moskal [this message]
2003-04-08 17:13 ` Brian Hurt
2003-04-08 19:23 ` Chris Hecker
2003-04-08 18:49 ` Karl Zilles
2003-04-08 19:04 ` Brian Hurt
2003-04-08 21:57 ` Daniel Andor
2003-04-08 22:07 ` Michal Moskal
2003-04-08 22:09 ` Brian Hurt
2003-04-10 2:59 ` cashin
2003-04-10 7:58 ` [Caml-list] { ... } vs ( ... ) vs begin ... end Frederic van der Plancke
2003-04-08 19:42 ` [Caml-list] single-line comment request Daniel M. Albro
2003-04-08 18:53 ` Alexander V. Voinov
2003-04-08 18:19 ` Nickolay Semyonov-Kolchin
2003-04-08 22:40 ` Joshua Scholar
2003-04-13 19:46 ` Andreas Rossberg
2003-04-13 22:57 ` Daniel M. Albro
2003-04-08 19:53 ` Jeff Henrikson
2003-04-08 20:31 ` Brian Hurt
2003-04-13 14:07 ` John Max Skaller
2003-04-08 15:28 ` Damien
2003-04-08 14:49 ` Nickolay Semyonov-Kolchin
2003-04-08 15:39 ` Brian Hurt
2003-04-08 15:45 ` malc
2003-04-08 15:45 ` Samuel Lacas
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=20030408213735.GA3061@roke.freak \
--to=malekith@pld-linux.org \
--cc=basile@starynkevitch.net \
--cc=brian.hurt@qlogic.com \
--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