From: Chris Hecker <checker@d6.com>
To: Nickolay Semyonov-Kolchin <snob@snob.spb.ru>,
Brian Hurt <brian.hurt@qlogic.com>
Cc: <caml-list@inria.fr>
Subject: Re: [Caml-list] single-line comment request
Date: Tue, 08 Apr 2003 09:31:12 -0800 [thread overview]
Message-ID: <4.3.2.7.2.20030408091635.037a29b0@localhost> (raw)
In-Reply-To: <200304081925.17114.snob@snob.spb.ru>
>Again, this extension is purely stylish.
Actually, just to fuel the fire, it's not just stylish. Single-line
comments are sometimes easier to work with programmatically (no need to
count {[()]} to see where the comment ends, rectangular editing commands
can comment and uncomment blocks, end of line is sometimes ragged so
commenting out cannot be done linearly without editor macro trickery,
wasted characters and movement for single line comments (which I would
assume are the majority of comments by number, if not by lines),
etc.). Also, using camlp4 for this slows down compiles.
I don't think this is the most important feature ever, but it would be nice
for more than just stylistic reasons.
I would assume there are lots of two-character combinations that are
invalid and that don't hose cpp, like "(|" which is even a bit iconographic
for the task, in my opinion. Somebody better at compilers than me could
probably write a program to parse the .y and .l files and generate all
unused and invalid two-character combinations.
Hmm, I just did a quick test to check the assumption of whether single-line
comments are more common. In my code, 86% of comments are single line. In
the compiler bytecomp directory, 89% are single line. Make of that what
you will.
Chris
-------------------
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 16:36 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 [this message]
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
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=4.3.2.7.2.20030408091635.037a29b0@localhost \
--to=checker@d6.com \
--cc=brian.hurt@qlogic.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).