Jon Lang wrote:
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'
raiph (>), Larry (>>):
>> 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, re
Perhaps we could name the incomplete releases "Rakudo Bikeshed".
Each release could be named after a popular color of bikeshed. The first
one should definitely be called "Rakudo White Bikeshed".
-j
Quoth markjr...@gmail.com (Mark J. Reed):
>
> 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.
I much prefer double-bracket to double-#: double-# gets caught out when
you do s/^/# on code which already includes line-s
# New Ticket Created by Carlin Bingham
# Please include the string: [perl #68402]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=68402 >
This is a basic patch to add a mkdir function. The (optional) mode
parameter uses the
Sorry for the delay in replying, but I was busy with other things and I
wanted to give other people a chance to reply. Since noone has, might it
be possible to get the attached patches committed? I'm not familiar with
the protocol for such things so, again, I'm sorry if I've got it wrong.
Ben
---
On Seg, 2009-08-10 at 22:06 -0500, raiph mellor wrote:
> > Rakudo Zengi would be the most (in)appropriate, I think.
> This latter point is the most exciting for me. "What is Rakudo Star?
> Well, it's..."
>
A Beatles drummer ?
-- Jose Celestino SAPO.pt::Systems http://www.sapo.pt
---
# New Ticket Created by Tim Bunce
# Please include the string: [perl #68416]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=68416 >
Being on holidays, it is not easy to follow threads closely, so if
I repeat things other people have said already, I apologize beforehand.
My responses may b late as well.
Two years ago, I discussed various options, which compared POD to features
in to other languages and suggested various syntax
Ben Morrow wrote:
> However, I would much rather see a general syntax like
>
> (# ... )
> {# ... }
> [# ... ]
>
> with no whitespace allowed between the opening bracket and the #: this
> doesn't seem to conflict with anything. Allowing <# ... > in rules would
> also be nice.
That's rather
smuj wrote:
> Jon Lang wrote:
>> 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 wi
Author: jani
Date: 2009-08-11 17:08:49 +0200 (Tue, 11 Aug 2009)
New Revision: 27957
Modified:
docs/Perl6/Spec/S09-data.pod
Log:
Clarification of hash key sort order, based on S32
Modified: docs/Perl6/Spec/S09-data.pod
===
--- docs
On Mon, Aug 10, 2009 at 10:31 AM, 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 begin
On Tue, Aug 11, 2009 at 8:59 AM, Jon Lang wrote:
> Ben Morrow wrote:
> > However, I would much rather see a general syntax like
> >
> >(# ... )
> >{# ... }
> >[# ... ]
> >
>
a preceding ':' (colon) makes it *notionally*
a null-label-block-comment-construct.
>
> > with no whitespace
Ben Morrow wrote:
> Quoth markjr...@gmail.com (Mark J. Reed):
>>
>> 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.
>
> I much prefer double-bracket to double-#: double-# gets caught out when
> you do s/^/# on code
Moritz Lenz writes:
> In all other cases of quote like constructs are the semantics are
> explicit first (think of Q, qx, m, <, «), the delimiter comes later.
> Changing that all of a sudden seems very unintuitive and wrong.
Thing is, comments are not quote-like. All of the quote-like
constru
Author: lwall
Date: 2009-08-11 19:28:07 +0200 (Tue, 11 Aug 2009)
New Revision: 27959
Modified:
docs/Perl6/Spec/S02-bits.pod
docs/Perl6/Spec/S04-control.pod
docs/Perl6/Spec/S05-regex.pod
docs/Perl6/Spec/S32-setting-library/Containers.pod
Log:
change embedded comment syntax to #`[...] an
At 6PM +0200 on 11/08/09 you (Moritz Lenz) wrote:
> Ben Morrow wrote:
> >
> > However, I would much rather see a general syntax like
> >
> > (# ... )
> > {# ... }
> > [# ... ]
> >
> > with no whitespace allowed between the opening bracket and the #: this
> > doesn't seem to conflict
Ben Morrow wrote:
> This appears to be leading to a :comment modifier on quotables, with
> some suitable shortcut. Perhaps 'q#'? Or are we not allowed mixed alpha
> and symbols?
It's probably a bad practice, if possible.
> (I really want to suggest £, just to teach USAnians '#' isn't called
> 'po
for the latest spec changes regarding this item, see
http://perlcabal.org/svn/pugs/revision/?rev=27959.
is everyone equally miserable now? ;)
~jerry
> for the latest spec changes regarding this item, see
> http://perlcabal.org/svn/pugs/revision/?rev=27959.
>
> is everyone equally miserable now? ;)
> ~jerry
Ha! :)
I do indeed feel underwhelmed. I'll surely get over it but I may as
well post why, even though Larry's presumably trying to stop th
jerry gay wrote:
> for the latest spec changes regarding this item, see
> http://perlcabal.org/svn/pugs/revision/?rev=27959.
>
> is everyone equally miserable now? ;)
Already seen it. My latest points still stand, though: #`(...) is
still vulnerable to ambiguity relative to #..., whereas `#(...),
jerry gay wrote:
for the latest spec changes regarding this item, see
http://perlcabal.org/svn/pugs/revision/?rev=27959.
is everyone equally miserable now? ;)
I'm quite happy actually -- #` or #+ makes no difference to me :-)
S02 just got that little bit simpler, so the thread was worthwhile.
This is an automatically generated mail to inform you that tests are now
available in t/spec/S02-builtin_data_types/whatever.t
commit f393f9c5b8f153e317cc29d4f072fce98dd053a0
Author: moritz
Date: Tue Aug 11 21:44:34 2009 +
[t/spec] test for RT #67450 - +* as array index
git-s
This is an automatically generated mail to inform you that tests are now
available in t/spec/S10-packages/basic.t
commit 14bcd61d38e8e0df7bdb18a0ce9d9ed539b23837
Author: kyle
Date: Wed Aug 12 01:06:05 2009 +
[t/spec] Test for RT #68290
git-svn-id: http://svn.pugscode.org/p...
This is an automatically generated mail to inform you that tests are now
available in t/spec/S05-match/capturing-contexts.t
commit 42de757ca2efdca487f23e54959612d7011f4d8c
Author: kyle
Date: Wed Aug 12 03:51:10 2009 +
[t/spec] Test for RT #64946
git-svn-id: http://svn.pugscod
This is an automatically generated mail to inform you that tests are now
available in t/spec/S05-match/capturing-contexts.t
commit 47c7c0d6a671619b234a9747c4107e48891e987b
Author: kyle
Date: Wed Aug 12 03:51:17 2009 +
[t/spec] Test for RT #64948
git-svn-id: http://svn.pugscod
Eirik Berg Hanssen wrote:
Moritz Lenz writes:
In all other cases of quote like constructs are the semantics are
explicit first (think of Q, qx, m, <, «), the delimiter comes later.
Changing that all of a sudden seems very unintuitive and wrong.
Thing is, comments are not quote-like. All of
28 matches
Mail list logo
