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 background or from a C++ background. I strongly dislike C++ and other than Perl primarily use C and shell, so # is the most natural to me and // looks really odd. Of course, like you said, we really can't use // anyway, as it's valid Perl code and actually semi-frequently used. I do agree that there's a lot to be said for using /* ... */ for multiline comments, but then I'm a C programmer. -- Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/>
- RFC: multiline comments Michael Mathews
- Re: RFC: multiline comments John Porter
- Re: RFC: multiline comments Michael Mathews
- Re: RFC: multiline comments Edwin Wiles
- Re: RFC: multiline comments Glenn Linderman
- Re: RFC: multiline comments Michael Mathews
- Re: RFC: multiline comments John Porter
- Re: RFC: multiline comments Edwin Wiles
- Re: RFC: multiline comment... Jarkko Hietaniemi
- Re: RFC: multiline comment... Jarkko Hietaniemi
- Re: RFC: multiline comment... Russ Allbery
- Re: RFC: multiline comment... Mike Pastore
- Re: RFC: multiline comment... Uri Guttman
- Re: RFC: multiline comments Tom Christiansen
- Re: RFC: multiline comments John Porter
- Re: RFC: multiline comment... Tom Christiansen
- Re: RFC: multiline comment... John Porter
- Re: RFC: multiline comment... Tom Christiansen
- Re: RFC: multiline comments Martyn J. Pearce
- Re: RFC: multiline comments Michael Fowler
- Re: RFC: multiline comments John Barnette