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 in column one. I think qc() should be allowed to look like perl code; but be discarded silently by the parser, inserting () or '' where appropriate to ensure silence: print "things:\n", qc/ show 'em all /, # replaced with empty list by compiler @things; print "total:\n" . qc{ show total } . # replaced with empty string by compiler $total; -- John Porter Aus tiefem Traum bin ich erwacht.
- Re: RFC: multiline comments Michael Fowler
- Re: RFC: multiline comments John Barnette
- Re: RFC: multiline comments Tim Jenness
- Re: RFC: multiline comments Michael Mathews
- Re: RFC: multiline comments John Barnette
- Re: RFC: multiline comments Johan Vromans
- Re: RFC: multiline comments Michael Mathews
- Re: RFC: multiline comments Tom Christiansen
- Re: RFC: multiline comments Michael Mathews
- Re: RFC: multiline comments Ted Ashton
- Re: RFC: multiline comments John Porter
- Re: RFC: multiline comments Michael Mathews
- Re: RFC: multiline comments John Porter
- Re: RFC: multiline comments Ted Ashton
- Re: RFC: multiline comments Glenn Linderman
- Re: RFC: multiline comments John Porter
- A Unicode fallacy [Was: Re: RFC... Glenn Linderman
- Re: A Unicode fallacy [Was: Re:... John Porter
- Re: A Unicode fallacy [Was: Re:... Glenn Linderman
- Re: A Unicode fallacy [Was: Re:... John Porter
- Re: A Unicode fallacy [Was: Re:... Glenn Linderman