FWIW for those wondering how exactly it was resolved, here's the commit:
https://github.com/rakudo/rakudo/commit/382c78a97ae6132d0054e0112cf19ceb2d50fef6
On 2016-12-10 10:10:48, c...@zoffix.com wrote:
> Tests now exist:
>
Yeah! It says this now:
===SORRY!=== Error while compiling ./test.pl
Couldn't find terminator ) (corresponding ( was at line 7)
at ./test.pl:10
-- BOL⏏EOL
expecting any of:
)
This can be closed.
On Fri, May 29, 2015 at 5:19 PM, Rob Hoelz via RT
perl6-bugs-follo...@perl.org
# New Ticket Created by Alex Jakimenko
# Please include the string: [perl #125247]
# in the subject line of all future correspondence about this issue.
# URL: https://rt.perl.org/Ticket/Display.html?id=125247
Code like this:
#!/usr/bin/env perl6
#`{{
some
comments
here
Gives this error
On Mon Mar 22 14:00:14 2010, lue wrote:
On Mon Mar 22 13:57:43 2010, lue wrote:
lue rakudo: #`hellothere
p6eval rakudo 35f337: OUTPUT«Confused at line 12, near
therecurrent instr.: 'perl6;HLL;Grammar;panic' pc 500
(ext/nqp-rx/src/stage0/HLL-s0.pir:328)»
lue you're right, it
# New Ticket Created by Life U. Everything
# Please include the string: [perl #73758]
# in the subject line of all future correspondence about this issue.
# URL: http://rt.perl.org/rt3/Ticket/Display.html?id=73758
lue rakudo: #`hello?there
p6eval rakudo 35f337: OUTPUT«Confused at line 12,
On Wed, Jan 02, 2008 at 11:28:54AM -0800, Jonathan Lang wrote:
: Paul Hodges wrote:
: http://perl6.org/doc/design/syn/S02.html still says:
: Intra-line comments will not be supported in standard Perl
:
: This is wrong, since S02 also defines intra-line comments, under
: Whitespace and
On Jan 3, 2008 6:36 PM, Larry Wall [EMAIL PROTECTED] wrote:
On Wed, Jan 02, 2008 at 11:28:54AM -0800, Jonathan Lang wrote:
: Paul Hodges wrote:
: http://perl6.org/doc/design/syn/S02.html still says:
: Intra-line comments will not be supported in standard Perl
Note that the document on
--- Jonathan Lang [EMAIL PROTECTED] wrote:
Paul Hodges wrote:
http://perl6.org/doc/design/syn/S02.html still says:
Intra-line comments will not be supported in standard Perl
This is wrong, since S02 also defines intra-line comments, under
Whitespace and Comments. It calls them
On Thu, Jan 03, 2008 at 08:55:24PM +0200, Gabor Szabo wrote:
: On Jan 3, 2008 6:36 PM, Larry Wall [EMAIL PROTECTED] wrote:
: On Wed, Jan 02, 2008 at 11:28:54AM -0800, Jonathan Lang wrote:
: : Paul Hodges wrote:
: : http://perl6.org/doc/design/syn/S02.html still says:
: : Intra-line comments
I love this list. I wish I had more of value to contribute. =o]
But for those of you who don't want to read a long blather, this is
mostly opinion, hopefully sans soapbox. Feel free to skip to the end.
asnideWhat's with the sudden influx of people swooping in at the
last minute and attacking
Paul Hodges wrote:
http://perl6.org/doc/design/syn/S02.html still says:
Intra-line comments will not be supported in standard Perl
This is wrong, since S02 also defines intra-line comments, under
Whitespace and Comments. It calls them 'embedded comments'. You
don't need a 'use' statement.
I've been putting a fair amount of thought into this. Here's what
I've come up with:
Perl 6 has several instances where whitespace is required or forbidden
in order to better facilitate Do What I Mean programming: for
instance, by having the presence or absence of whitespace before curly
braces
Jonathan Lang wrote:
How about '~#', meaning something along the lines of string-like
comment? The idea is that the syntax that follows this would conform
closely to that of string literals (i.e., quotes). We might even
consider loosening the restrictions on delimiter characters, allowing
Christian Mueller wrote:
i don't know the actually state in the discussion about multiline
comments, but i would propose an idea.. a combination of POD's = and the
traditional route char...
Perl 6 already has a robust system for multiline and embedded
comments, as described in S02 under
On 30/12/2007, Jonathan Lang [EMAIL PROTECTED] wrote:
The only wart
is that '#( ... )' cannot begin at the very start of a line; but it's
easy enough to get around that restriction - say, with some leading
whitespace.
Thanks for the reply - can you please what is the problem with having
it in
Amir E. Aharoni wrote:
On 30/12/2007, Jonathan Lang [EMAIL PROTECTED] wrote:
The only wart
is that '#( ... )' cannot begin at the very start of a line; but it's
easy enough to get around that restriction - say, with some leading
whitespace.
Thanks for the reply - can you please what is
On Dec 30, 2007 6:10 PM, Jonathan Lang wrote:
Short answer: the compiler has no way of knowing whether the
programmer wants an embedded comment or a line comment; so instead of
guessing, it requires the programmer to disambiguate.
[...snip...]
# if ($test)
# {
.say;
# } else
Whitespace is significant in many places. Even in some of the corners
of Perl 5. Perl 6 has a different set of rules, and it will take some
getting used to, but the rules are designed to let you do things as
naturally as possible.This, for instance, works fine:
my @values =
# (1,2,3) #
Offer Kaye wrote:
#( commenting out a large code section, yey for Perl6 multi-line comments...
if ($foo) {
print ...or not :(\n
}
) # this should have been the end of the embedded comment
...and since it wasn't, you probably should have chosen other brackets such as:
#[[
.
Is it not possible to skip the commented sections by the parser?
Why have every other popular language, that i know, multiline comments
included without any problems? It would be very useful for better
developing with perl.
If you would use a mlc like =# #= where the opening tag must stay
On Dec 30, 2007 8:10 AM, Jonathan Lang [EMAIL PROTECTED] wrote:
Let's say that the programmer in question wants to comment out all but
the third line; so he prefixes everything else with '#':
#if ($test)
#{
.say;
#} else {
# .doit;
#}
What the writer _wants_ this to do is the
Hello list,
i don't know the actually state in the discussion about multiline
comments, but i would propose an idea.. a combination of POD's = and the
traditional route char...
=#
this is a multi
line comment
#=
=# comment #= this is not commented
What you think about it?
regards
Christian
On 12/10/2005, at 3:33 PM, Luke Palmer wrote:
On 10/11/05, Alfie John [EMAIL PROTECTED] wrote:
Does Perl6 support multiline comments?
Yes, in the form of pod blocks.
=begin comment
=end comment
They nest, too.
Luke
But does that then break my lovely formatted pod like it does
Alfie John wrote:
Hi (),
This is probably a stupid question, but I can't find anything from google:
Does Perl6 support multiline comments?
Briefly, No and kind of.
Standard Perl 6 comments are just like those in Perl 5. A '#' starts a
comment that is terminated by the end of line
On 12/10/2005, at 4:18 PM, Mark A. Biggar wrote:
Alfie John wrote:
Hi (),
This is probably a stupid question, but I can't find anything
from google:
Does Perl6 support multiline comments?
Briefly, No and kind of.
Standard Perl 6 comments are just like those in Perl 5. A '#'
starts
On 10/12/05, Alfie John [EMAIL PROTECTED] wrote:
On 12/10/2005, at 3:33 PM, Luke Palmer wrote:
=begin comment
=end comment
But does that then break my lovely formatted pod like it does in Perl5?
Try this:
% cat dosomething.pl
=head1 TITLE
Thingy - do something
=head1 DESCRIPTION
=over
Alfie John skribis 2005-10-12 15:28 (+1000):
Does Perl6 support multiline comments?
All incarnations of Perl have allowed us to begin multiple subsequent
lines with the comment glyph '#'. I am sure Perl 6 will not break this
tradition.
Juerd
--
http://convolution.nl/maak_juerd_blij.html
http
It was just kind of a pain because you
had to put a =cut after the =end, and because you had to put
paragraph spaces between everything. We're getting rid of both of
those restrictions.
Excellent! That's what was really bugging me. I'm really glad that is
changing :)
Thanks,
Alfie
Hi (),
This is probably a stupid question, but I can't find anything from
google:
Does Perl6 support multiline comments?
Alfie John
On 10/11/05, Alfie John [EMAIL PROTECTED] wrote:
Does Perl6 support multiline comments?
Yes, in the form of pod blocks.
=begin comment
=end comment
They nest, too.
Luke
30 matches
Mail list logo
