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
[EMAIL PROTECTED] wrote:
> +++ doc/trunk/design/syn/S03.pod Fri Feb 2 01:07:36 2007
> +Both of these forms actually translate to
> +
> +if $filename.TEST(:e) { say "exists" }
> +
> +which which is a generic mechanism that dispatches to the object's
> +class to find the definition of C. (It
[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
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 fin
[EMAIL PROTECTED] wrote:
Modified: doc/trunk/design/syn/S09.pod
==
...
-my @calendar[12;*;24]; # "Month" dimension unlimited
+my @calendar[12;*;24]; # day-of-month dimension unlimited/ragged
There's
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
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
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 Turin
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.ba
Damian Conway wrote:
> Any subroutine/function like C that has a signature (parameter list)
> that ends in a C<&sub> argument can be parsed without the trailing
> semicolon. So C's signature is:
>
> sub if (bool $condition, &block);
So what does the signature for C look like? I've been w
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
-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
> decl
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:
>
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? Th
From: Michael Lazzaro [mailto:[EMAIL PROTECTED]]
> But I don't know if these two
> lines would really have the same result, ...
>
> $a = MyScalar;
> $a = 'MyScalar';
Hrmm. Didn't Larry decree that there are no bare words, but that a class
name will evaluate to the string representing th
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
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! Al
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
learne
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 C, is that it eliminates
the dangling-else ambiguity -- so splitting it
Smylers wrote:
Thom Boyer wrote:
The primary advantage, to my mind, in using C, is that it
eliminates the dangling-else ambiguity -- so splitting it in half
removes almost ALL the value of even having an C keyword.
Surely it's the compulsory braces, even with a single statement,
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 IIR
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 _appearanc
From S02:
The double angles may be written either with French quotes, «$foo
@bar[]»||, or with "Texas" quotes, <<$foo @bar[]>>,|| as the ASCII
workaround.
---
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, <<$fo
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
*** wiki
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, a
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
S02 mentions "identifier extensions" in the section describing adverbial
pairs with non-identifier keys (see the table reproduced below).
What are identifier extensions? I'm guessing that : and :<+> are
both acting as identifier extensions in these examples:
statement_control:
infix:<
S02 says "A bare closure also interpolates in double-quotish context."
I presume that there are no restrictions on the code inside that
closure, but all the examples I've seen have nothing but expressions
inside the closure (though some examples, admittedly, do invoke subs
and/or methods).
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 "
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
Thom Boyer wrote:
Now, I think that
$x.foo
is a method call, even if there's a postfix: declaration in scope.
And that's a problem, because, no matter what precedence postfix:
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!
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
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 single
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?
>>
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 on
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 I in the vernacular)).
The best that I can figure for "blast" is
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
39 matches
Mail list logo
