caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Jeff Henrikson <jehenrik@yahoo.com>
To: caml-list@inria.fr
Cc: Nickolay Semyonov-Kolchin <snob@snob.spb.ru>
Subject: Re: [Caml-list] single-line comment request
Date: Tue, 8 Apr 2003 15:53:38 -0400	[thread overview]
Message-ID: <CA533CFA-69FB-11D7-81FD-00039375801A@yahoo.com> (raw)
In-Reply-To: <4.3.2.7.2.20030408110617.0389bde8@localhost>

Though I favor the addition of the single line comments, most of the 
comments thus far seem to be very subjective.  I find the "80+ percent 
of comments in the existing sources are single line comment" fairly 
weighty.  I also find the following unmentioned idea significant: 
single line comments save large number of keystrokes when substituting 
different chunks of code during testing.  Also adding printfs.  And any 
comment-compile-uncomment-compile situation.  It's a fairly specific 
task, but also a pronounced difference when it happens.

I find a lot of the "no-single-comment" arguments to be sounding 
remarkably reductionist in the way the "we don't need GUI" arguments 
that certain die hard UNIX users purvey.  The comment character is a 
user interface for a programming language.  Let's make it a nice one.  
OCaml already breaks backward compatibility often.  And for whatever 
branches of OCaml are out there, any backport would be trivial.

BTW, I kind of don't like ##, because it's a shift key.  There are no 
single char symbols left, okay.  But that's true for C(++) as well, 
hence the "//".  What's wrong with //?  I see that it's an "operator 
char" in the language definition lexical conventions.  I'm not sure if 
that's a big deal.  I'd like "--" also.  Same op-ch issue.


Jeff Henrikson

-------------------
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


  parent reply	other threads:[~2003-04-08 19:53 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
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 [this message]
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=CA533CFA-69FB-11D7-81FD-00039375801A@yahoo.com \
    --to=jehenrik@yahoo.com \
    --cc=caml-list@inria.fr \
    --cc=snob@snob.spb.ru \
    /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).