Of all the variations that I've seen so far (I'm way behind on reading
the list), the one I like the best is:
qc{ multi
line
comment
here }
Second best, but still acceptable would be:
#END
multi
line
comment
END
The reason it's second best, is because qc{ canbeusedinline } as well as
I should read what has been said about the matter earlier...but
lacking the time, I'll just shoot:
What's wrong with stealing from C/C++/Java instead
of trying to invent our own?
In other words, what's wrong with /* ... */?
--
$jhi++; # http://www.iki.fi/jhi/
#
I also confess to liking // more for till-end-of-line comment marker
than #, the hash looks so messy to my eye...of course, // already has
a meaning...
--
$jhi++; # http://www.iki.fi/jhi/
# There is this special biologist word we use for 'stable'.
# It is 'dead'. -- Jack Cohen
Jarkko Hietaniemi [EMAIL PROTECTED] writes:
I also confess to liking // more for till-end-of-line comment marker
than #, the hash looks so messy to my eye...of course, // already has
a meaning...
I'm the other way around.
This may depend a lot on whether one comes from a shell scripting
Russ Allbery wrote:
Jarkko Hietaniemi [EMAIL PROTECTED] writes:
I also confess to liking // more for till-end-of-line comment marker
than #, the hash looks so messy to my eye...of course, // already has
a meaning...
I'm the other way around.
This may depend a lot on whether one
please move this thread to the mlc list.
thanx,
uri
--
Uri Guttman - [EMAIL PROTECTED] -- http://www.sysarch.com
SYStems ARCHitecture, Software Engineering, Perl, Internet, UNIX Consulting
The Perl Books Page --- http://www.sysarch.com/cgi-bin/perl_books
The
The message below gives the context for this diatribe.
A perl script is probably written in a particular language, probably for
users of that language, possibly for users of a second language. Unless
there are lots of I18N type features added into Perl to allow extracting
all string constants
Glenn Linderman wrote:
Stick with characters in the normal character set of the author of the
script, except for forays into the language of the users of the script.
Good advice for the programmer, perhaps; but it should not be perl's
job to enforce that discipline.
--
John Porter
John Porter wrote:
Glenn Linderman wrote:
Stick with characters in the normal character set of the author of the
script, except for forays into the language of the users of the script.
Good advice for the programmer, perhaps; but it should not be perl's
job to enforce that discipline.
John Porter wrote:
Michael Mathews wrote:
Using a two-character syntax to start and end a multiline comment seems to
be a good way to satisfy both the desired similarity to "#" and the desired
uniqueness to avoid collision with real single-line quotes. I would suggest
a (# many lines
Thus it was written in the epistle of Michael Mathews,
Ted Ashton wrote:
The qc()
proposal fits in well with the Perl "look-and-feel" and seems pretty
comfortable to me. If there are concerns about obfuscatory potential, a
use strict 'comments' could require that the qc( opening start
Ted Ashton wrote:
2) Also this proposition fails in one of my goals, which was to allow
arbitrary nesting of multiline comments. I believe this would be true for
any function based solution.
Negative. If you use paired delimiters you're ok.
qc( Here's a quick comment which actually
Glenn Linderman wrote:
$foo = $a + $b # can this be an in-line comment? # + $c * $d;
Note that with this scheme it would be possible to allow in-line comments
to be
multi-line comments, or possible to prevent that. I'd vote in favor of
keeping
in-line comments on a single line.
Note
Glenn Linderman wrote:
qc( Here's a quick comment which actually contains
qc( another comment )
within it
);
This type of comment will not comment out arbitrary text.
In particular, it might have problems with text containing
mismatched (){}.
This is already an issue
Michael Mathews wrote:
So this should work in Perl 6
code here;
#
# this is a single line comment
$foo = $a + $b # here's an in-line comment # + $c * $d;
#
more code here;
If starting in column 1 is going to be magic, you may as well
make the magic char #, so:
#
# this is
This seems like an acceptable variation on what has been suggested so far. I
deally one would be able to safely block comment any large section of a Perl
6 script and not worry about any other block comments within (the outermost
block comment takes precedence).
I still like this solution
Proposal: here-docs specified with regexes, and no special
meaning for newlines.
comment /EOC/; this is an arbitrary comment. EOC
Smack--the lexer cowers before you!
--tom
Tom Christiansen wrote:
comment /EOC/; this is an arbitrary comment. EOC
Smack--the lexer cowers before you!
Well, hey, while we're daydreaming... :-)
--
John Porter
On Wed, Aug 02, 2000 at 03:00:04PM -0400, Michael Mathews wrote:
Ted Ashton wrote:
The qc()
proposal fits in well with the Perl "look-and-feel" and seems pretty
comfortable to me. If there are concerns about obfuscatory potential, a
use strict 'comments' could require that the qc(
19 matches
Mail list logo
