Woops - forgot to reply all (I'm on an irritating mixture of lists
which set reply-to and don't, and I never remember which is which).
Sorry!
-- Forwarded message --
From: Matthew Walton
Date: Tue, Aug 11, 2009 at 7:10 AM
Subject: Re: More flexible POD
To: Jon Lang
I'm not sur
> Rakudo Zengi would be the most (in)appropriate, I think.
Why do I get the sense that some in the community are suffering siege
mentality? ;)
I had thought of things like Zen, Zero, Catalyst, etc.
But I love * | Star | Whatever. I love:
o The word Star, regardless of its connection with Perl
smuj wrote:
> Jon Lang wrote:
>> Here's a radical notion: use something other than '#' to initiate an
>> inline comment.
>>
> [snippage]
>
> Or maybe just don't allow "embedded" comments unless they are actually
> "embedded", i.e. if a line starts with a # (ignoring leading whitespace)
> then it's
Jon Lang wrote:
smuj wrote:
smuj wrote:
Jon Lang wrote:
... the biggest potential stumbling block for this
would be the existence of a double-bracket that sees frequent use at
the start of a line. Query: does '<<' count as a double bracket, or
as a single bracket (since it's equivalent to '«'
Rakudo Zengi would be the most (in)appropriate, I think.
Larry
Darren Duncan wrote:
> Still, I like the idea of #...# also being supported from the point of
> symmetry with '...' and "..." also being supported, not that this is
> necessary.
This is mutually exclusive with the practice of commenting out a bunch
of lines by prepending them with '#'.
--
Jonath
smuj wrote:
> smuj wrote:
>> Jon Lang wrote:
>>> ... the biggest potential stumbling block for this
>>> would be the existence of a double-bracket that sees frequent use at
>>> the start of a line. Query: does '<<' count as a double bracket, or
>>> as a single bracket (since it's equivalent to '«'
Jon Lang wrote:
On Mon, Aug 10, 2009 at 3:36 PM, Darren Duncan wrote:
Personally, I think that comments should have trailing # as well as leading
ones, so they are more like strings in that the same character is used to
mark both ends.
You mean like the following?
q[quoted text]
qq(in
Since I don't know anything about nuclear power plants, I think the BikeShed
should be painted blue and called "Rakudo Whatever" or just "Rakudo".
-Jason "s1n" Switzer
smuj wrote:
Jon Lang wrote:
On Mon, Aug 10, 2009 at 2:16 PM, Mark J. Reed wrote:
I still like the double-bracket idea. I don't much mind the extra
character; 5 characters total still beats the 7 of HTML/XML.
Agreed. As I said, the biggest potential stumbling block for this
would be the exist
On Mon, Aug 10, 2009 at 3:36 PM, Darren Duncan wrote:
> Personally, I think that comments should have trailing # as well as leading
> ones, so they are more like strings in that the same character is used to
> mark both ends.
You mean like the following?
q[quoted text]
qq(interpolated quo
As an addendum, I think it goes without saying that this is the simplest form of
what I proposed:
# This is a
comment. #
That denotes a complete comment, which could be broken over lines or not, and
the rules for parsing or escaping it would be exactly the same as a character
string litera
Personally, I think that comments should have trailing # as well as leading
ones, so they are more like strings in that the same character is used to mark
both ends.
So in combination with bracketing pairs, we could for example have this:
#{ This is a comment. }#
That also serves to make th
Masak's Journal[1] identifies a couple of problems involving the
interaction of POD with block-form classes - one in the article
itself, and another in the comments that follow. The first is that a
mixture of indented block-form classes and non-indented POD is
visually very ugly. The second is th
This is an automatically generated mail to inform you that tests are now
available in t/spec/S02-builtin_data_types/anon_block.t
commit 649dc2cb2a29b472f30c35d88b4c3ac66e9a19f1
Author: kyle
Date: Mon Aug 10 21:51:55 2009 +
[t/spec] Test for RT #68116
git-svn-id: http://svn.pu
This is an automatically generated mail to inform you that tests are now
available in t/spec/S06-multi/syntax.t
commit 71dc6c2454e83fb2ca5bc7c424d8284f906fcefd
Author: kyle
Date: Mon Aug 10 21:51:49 2009 +
[t/spec] Test for RT #68234
git-svn-id: http://svn.pugscode.org/p...@2
Jon Lang wrote:
On Mon, Aug 10, 2009 at 2:16 PM, Mark J. Reed wrote:
I still like the double-bracket idea. I don't much mind the extra
character; 5 characters total still beats the 7 of HTML/XML.
Agreed. As I said, the biggest potential stumbling block for this
would be the existence of a dou
On Mon, Aug 10, 2009 at 2:16 PM, Mark J. Reed wrote:
> I still like the double-bracket idea. I don't much mind the extra
> character; 5 characters total still beats the 7 of HTML/XML.
Agreed. As I said, the biggest potential stumbling block for this
would be the existence of a double-bracket that
On Mon, Aug 10, 2009 at 4:57 PM, Jon Lang wrote:
> I'd recommend '#='; but if that
> isn't already being used by pod, it should be reserved for use by pod
> (and it's visually heavy).
Commenting out lines that include pod will generate #= at the
beginning of a line, which is tantamount to the prob
On Mon, Aug 10, 2009 at 12:25 PM, Patrick R. Michaud wrote:
> I'd be fine with the ##(embedded comment solution) approach (doubling
> the #'s), but it's much less visually appealing to me. I think I'd
> prefer to see a doubling of the bracketing chars instead of doubling
> the #'s -- the # is visu
Patrick R. Michaud wrote:
On Mon, Aug 10, 2009 at 06:46:34PM +0100, smuj wrote:
Although I can see some minimal uses for embedded comments, I think in
general the cost/benefit ratio isn't enough to warrant their existence.
I could be wrong of course! :-) I'd like to know if anyone has made mu
On Mon, Aug 10, 2009 at 06:46:34PM +0100, smuj wrote:
> Although I can see some minimal uses for embedded comments, I think in
> general the cost/benefit ratio isn't enough to warrant their existence.
> I could be wrong of course! :-) I'd like to know if anyone has made much
> use of them in
Modifiers like :ratchet are lexically scoped, and therefore extend
into any embedded or , I think. These days
if you find yourself saying "surrounding context", you should usually
ask yourself whether you mean "lexical" or "dynamic", and that often
indicates the direction I'll be leaning on under
Hiyas,
Carl Mäsak wrote:
In my post "Three things in Perl 6 that aren't so great" [0], I
outline three things about Perl 6 that bug me at present. Commenter
daxim made what seems to me a sensible proposal [1] for solving the
third problem, "Comments in the beginning of lines":
daxim (]):
] Let
This is an automatically generated mail to inform you that tests are now
available in t/spec/S02-names/identifier.t
commit 03e3b22b950c72abd52962a6283ba2b8c8a4f2cb
Author: kyle
Date: Mon Aug 10 16:50:36 2009 +
[t/spec] Test for RT #68358
git-svn-id: http://svn.pugscode.org/p.
In my post "Three things in Perl 6 that aren't so great" [0], I
outline three things about Perl 6 that bug me at present. Commenter
daxim made what seems to me a sensible proposal [1] for solving the
third problem, "Comments in the beginning of lines":
daxim (]):
] Let single # be used for comment
This is an automatically generated mail to inform you that tests are now
available in t/spec/S12-attributes/instance.t
commit 93c0f5aef4ded4abcb4397deb630eba51f6f412e
Author: kyle
Date: Mon Aug 10 15:50:12 2009 +
[t/spec] Test for RT #68370
git-svn-id: http://svn.pugscode.org
On Sun Aug 09 14:56:24 2009, moritz wrote:
> It seems that the :foo[...] colonpair syntax doesn't set up the array
> sufficiently non-flattening:
Correct, Rakudo doesn't handle the non-paren colonpair syntaxes yet
(they were recently refactored in STD.pm and haven't caught up). This
ticket is rea
# New Ticket Created by "Carl Mäsak"
# Please include the string: [perl #68350]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=68350 >
rakudo: for 1,2,3,4,5 -> $a, $? { say $a }
rakudo 5c4b1b: OUTPUT«Invalid twigil used i
Parrot Bug Summary
http://rt.perl.org/rt3/NoAuth/parrot/Overview.html
Generated at Mon Aug 10 12:35:43 2009 GMT
---
* Numbers
* New Issues
* Overview of Open Issues
* Ticket Status By Version
* Requestors with m
# New Ticket Created by "Carl Mäsak"
# Please include the string: [perl #68370]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=68370 >
Rakudo a948cae:
$ perl6 -e 'class A { has $!a; method foo() { $!a = 42 } }; A.foo'
Null
# New Ticket Created by "Carl Mäsak"
# Please include the string: [perl #68356]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=68356 >
rakudo: my $x = bar => [ baz => 42, sloth => 43 ]; my $y =
:bar[ baz => 42, sloth => 43
Given the Japanese behind the name Rakudo, "rakudone" looks like a
question: "Rakudo, right?" Beats "rakuod", though.
On 8/10/09, James Fuller wrote:
> how about
>
> 'raku'
>
> then the final version could be called
>
> 'rakudone'
>
> Jim Fuller
>
--
Sent from my mobile device
Mark J. Reed
how about
'raku'
then the final version could be called
'rakudone'
Jim Fuller
# New Ticket Created by "Carl Mäsak"
# Please include the string: [perl #68358]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=68358 >
rakudo: my($a) = 5; say 'alive'
rakudo 61f269: OUTPUT«alive»
* masak submits rakudobu
# New Ticket Created by "Carl Mäsak"
# Please include the string: [perl #68346]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=68346 >
rakudo: regex foo { foo }; say foo('foo').perl
rakudo 5667dc: OUTPUT«Method 'perl' not
Then you could be like TeX and have releases numbered with
ever-increasing parts of an irrational number.
On Mon, Aug 10, 2009 at 12:37 PM, Mark J. Reed wrote:
> Wrong reply button...
>
> -- Forwarded message --
> From: "Mark J. Reed"
> Date: Mon, 10 Aug 2009 07:36:52 -0400
> Subj
Wrong reply button...
-- Forwarded message --
From: "Mark J. Reed"
Date: Mon, 10 Aug 2009 07:36:52 -0400
Subject: Re: Rukudo-Star => Rakudo-lite?
To: Gabor Szabo
That has the same problem as lots of other themes - it puts a hard
limit on the number of releases before the One Tru
On Mon, Aug 10, 2009 at 2:02 AM, Patrick R. Michaud wrote:
> On Sun, Aug 09, 2009 at 04:35:42PM -0600, David Green wrote:
>> On 2009-Aug-9, at 3:57 pm, Tim Bunce wrote:
>>> Perhaps it's worth asking what we might call the release after that
>>> one.
>>> "Rakudo not-quite-so-lite"?
>>
>> Rakudo ** (
On Sun, Aug 9, 2009 at 4:22 PM, Carl Mäsak wrote:
>
> Dunno, but I just tried that command and had no problems at all.
Same here now, worked like a charm this time. Must have been a temp
network problem.
Thanks all,
--
Offer Kaye
40 matches
Mail list logo
