pugs-comm...@feather.perl6.nl wrote:
Author: lwall
Date: 2009-11-19 05:34:29 +0100 (Thu, 19 Nov 2009)
New Revision: 29129
Modified:
docs/Perl6/Spec/S04-control.pod
Log:
[S04] as several folks have suggested, rename blorst to blast
I'm curious about this change. I quickly figured out that
I'm curious about the change from blorst to blast. I quickly figured out
that blorst was
derived from BLock OR STatement (as S04 used to say: In fact,
most of these phasers will take either a block or a statement (known as
a Iblorst in the vernacular)).
The best that I can figure for blast is
Patrick R. Michaud wrote:
my $foo = [ 42 ];
my $bar = { a = 23 };
$foo[1] = $bar;
TSa (Thomas Sandlaß) wrote:
I would also opt for copy semantics whenever = is used for assignment.
But C$foo[1] = $bar *does* use copy semantics. The thing on the right
is a reference to a hash, and
Mark J. Reed wrote:
It would behoove @Larry to examine the optional type constraints
system proposed for Javascript:TNG (see link from firefox.com
developers page). I therefore assume that they have done so, but
others would benefit by doing likewise. :)
Could you be a little more specific
Larry Wall wrote:
How private is private? I wonder if what you've called private
things are really more like protected in C++ (accessible by the
derived class) and that 'my' attributes are really private, as are
submethods. It's all confused. Who is allowed to access what?
No, private
Thom Boyer wrote:
Now, I think that
$x.foo
is a method call, even if there's a postfix:foo declaration in scope.
And that's a problem, because, no matter what precedence postfix:foo
was given,
1,2,3.foo
is still going to mean
1, 2, (3.foo)
instead of the desired
Thom Boyer wrote:
And does dot always do that? If it does, then something odd happens.
Consider infix:* and postfix:!, where infix:* binds tighter than
postfix:+, and both bind more loosely than dot. Then
I meant ... tighter than postfix:!, ...
1 * 2! # means (1 * 2)!
1 * 2
Jon Lang wrote:
Thom Boyer wrote:
That seems better to me than saying that there's no tab character in
say blah $x\t blah
Whoever said that?
Oops. I thought Larry did. But he didn't; I misread it. Whew.
Somehow I managed to read Larry's words and get exactly the *opposite*
meaning
Larry Wall wrote:
The .++ form is still not a method (single) dispatch, just an alternate
form of the postfix, which is a multi dispatch.
But the postfix is a unary operator, right? So that'd be multi dispatch
on one argument.
How does single dispatch differ from multi dispatch on a
Larry Wall wrote:
On Wed, Mar 26, 2008 at 12:56:08PM -0600, Thom Boyer wrote:
Larry Wall wrote:
... In the
limit, suppose some defines a postfix say looser than comma:
(1,2,3)say
1,2,3say
1,2,3.say
I must be missing something. Wouldn't it be easier to write
1,2,3 say
since
S02 provides this example for treating curlies literally in a quoted string:
qq:!c Here are { $two uninterpolated } curlies;
But can I escape them with a backslash? I was surprised that I couldn't
find anything in S02 which said either yes or no. Perhaps this falls
under the heading of
Joe Gottman wrote:
In the definition of cmp, S29 says the function returns
|Order::Increase|, |Order::Decrease|, or |Order::Same| (which numify
to -1, 0, +1). Shouldn't the enumerations and their numerical values
be listed in the same order?
Joe Gottman
The enumerations and the numerical
Chas. Owens wrote:
Like a true Texan* (grin), he skewed the numbers to make Texas look
bigger than it is. It is between 2.4** and 2.5*** when you include
...
* I am resident of Virgina, so I have no axe to grind; I am just
looking for a definitive answer.
** random sites on the Internet
***
Larry Wall wrote:
On Thu, Dec 06, 2007 at 09:36:36AM -0700, Thom Boyer wrote:
From S02:
The double angles may be written either with French quotes, «$foo
@bar[]»||, or with Texas quotes, $foo @bar
Jonathan Lang wrote:
2. Getting block comments to hide POD blocks wouldn't require the POD
parser to have a full implementation of a Perl parser. It would
require the POD parser to have a _limited_ implementation of a Perl
parser, one that's capable of identifying block comments. And IIRC,
Thomas Wittek wrote:
I mean POD uses constructs like headlines, lists, blocks, italic etc.
which all describe _how it looks like_ and not _what it is_.
I think Damian would take exception to that statement. He worked quite
hard to make sure that POD describes _meaning_ rather than
I never could find the Pod-to-XHTML'd version of S26 -- the document
attached to that email was S26.pod6, not S26.xhtml.
I don't want to bug Damian, because obviously he has enough of life
happening, as it were. But is the XHTML'd version of S26 available
anywhere? I haven't been able to find
[EMAIL PROTECTED] wrote:
Modified: doc/trunk/design/syn/S03.pod
==
...
+Alternately, you can increment a submatch:
+
+$filename ~~ s[^.* (\w+) \.\w+$] = $().succ;
+
Don't you want the leading .* to be
On 8/16/06, Agent Zhang [EMAIL PROTECTED] wrote:
On 8/17/06, Mark J. Reed [EMAIL PROTECTED] wrote:
Where can I find a pod2html that groks the p6 version of POD? I want
to format my fresh-from-svn copies of the doc...
...
And there're also an online HTML version of the Perl 6 Spec:
On 10/20/05, Juerd [EMAIL PROTECTED] wrote:
Larry Wall skribis 2005-10-20 7:56 (-0700):
the new sigil is the cent sign, so ::T is now written ¢T instead.
1. What does it look like? I've never used a cent sign, and have seen
several.
It looks like a lowercase c with a vertical line through
Smylers wrote:
Thom Boyer wrote:
The primary advantage, to my mind, in using Celsif, is that it
eliminates the dangling-else ambiguity -- so splitting it in half
removes almost ALL the value of even having an Celsif keyword.
Surely it's the compulsory braces, even with a single statement
Smylers [mailto:[EMAIL PROTECTED]] wrote:
And an alternative
spelling for the assignment operator[*0] doesn't strike me as something
Perl is really missing:
$msg ~ 'Hello there';
$msg = 'Hello there';
I still remember the first time I saw a computer program, before I had
learned
Rafael Garcia-Suarez [mailto:[EMAIL PROTECTED]] wrote:
The tokeniser could send two tokens else and if whenever it
recognizes the keyword elsif -- so this isn't a problem.
The primary advantage, to my mind, in using Celsif, is that it eliminates
the dangling-else ambiguity -- so splitting it in
Paul Johnson [EMAIL PROTECTED] wrote:
When I later saw it using mutt in an xterm, the tilde was at the top of
the character, where I was more used to seeing it and it didn't look like
an arrow any more, nor did it look very good to me.
Well, at least now I understand why some people didn't see
Andrew Rodland [EMAIL PROTECTED] wrote:
But you're missing the most important part!
I propose that these operators should be named gozinta ( ~)
and comezouta ( ~ ), just so that we can say that perl has them. Not to
mention that the names work pretty well, for me.
Here, here! All in favor,
Mr. Nobody [EMAIL PROTECTED] wrote:
--- Damian Conway [EMAIL PROTECTED] wrote:
@a ~ grep {...} ~ map {...} ~ sort ~ @out;
That's going to be just plain confusing. Arguments to functions are
supposed
to be on the right. And what's up with using them for assignment? That's
making
-Original Message-
Rafael Garcia-Suarez [EMAIL PROTECTED] wrote:
Actually I don't think you can define a grammar where two operators have
the same precedence but different associativity. Be it a pure BNF
grammar, or a classical yacc specification (using the %left and %right
On Wednesday, November 06, 2002, at 11:54 AM, Michael Lazzaro wrote:
On Tuesday, November 5, 2002, at 11:18 PM, Allison Randal wrote:
Since you're interested in the management of the Perl 6 project, I'll
let you in on some of it. Let's start with a step back into a bit of
history:
OK,
Damian Conway wrote:
Any subroutine/function like Cif that has a signature (parameter list)
that ends in a Csub argument can be parsed without the trailing
semicolon. So Cif's signature is:
sub if (bool $condition, block);
So what does the signature for Cwhile look like? I've been
Trey wrote:
I'm wondering about how the sigil-invariance rule interacts with
attributes.
class Foo {
attr $bar;
attr bar;
method baz {
return .bar[$.bar]; # sigils disambiguate
}
method frob ($self:) {
return $self.bar[$self.bar]; #
Steve Find said on August 09, 2002 6:24 PM:
Anyone happen to know where pushdown automata fit in this list? Can
they handle context-sensitive, just context-free, or some other
subset?
Mark Reed said on August 09, 2002 7:60 PM:
To recognize a context-sensitive language I think you need a Turing
Peter Scott wrote:
At 01:54 PM 7/3/02 -0600, Thom Boyer wrote:
I'm personally MUCH more interested in Python's generators
http://www.python.org/peps/pep-0255.html.
A generator is like an iterator in that it can produce
a series of values. But unlike iterators, when you ask
a generator
On Tue, 02 Jul 2002 10:36:45 -0700, Erik Steven Harrisan wrote:
ESH my $a = 'foo';
ESH
ESH pass_by_name ( sub { print $a} );
ESH
ESH sub pass_by_name {
ESH my $a = 'bar';
ESH _[0];
ESH }
ESH
ESH Now, I have trouble keeping Perl 6 and 5 straight, but what I think
33 matches
Mail list logo
