Author: autrijus
Date: Sat Apr 22 00:22:21 2006
New Revision: 8908
Modified:
doc/trunk/design/syn/S03.pod
Log:
* S03: Document that C and C forms are not declarators.
Modified: doc/trunk/design/syn/S03.pod
==
--- doc/
> return a boolean for either 1 or 0 arguments. Negated operators,
> -return Bool::False, and all the rest return Bool::True.
> +return C, and all the rest return C.
The comma on the first line is superfluous.
--
I will take my life into my hands And I will use it.'MacArthur Park'
I will w
During my S03 cleanup today, I noticed that because *$fh and **$fh
interpolates into the current argument list, it's always the same as
=$fh under list context. So I wrote this paragraph:
[Conjectural: File handles interpolates its lines into positional
arguments (e.g. to C>), so we can make C<=$
Author: autrijus
Date: Sat Apr 22 03:04:09 2006
New Revision: 8909
Modified:
doc/trunk/design/syn/S03.pod
Log:
* S03: Clarify that C<*> does not really provide list
context to its operand; rather, it injects the
operand to the currnent argument.
Modified: doc/trunk/design/syn/S0
Here are two comments after reading S05, Version 18 at
http://dev.perl.org/perl6/doc/design/syn/S05.html
In section "Extensible metasyntax (<...>)"
With both bare hash and hash in angles, the key is always skipped over
before calling any subrule in the value. That subrule may, however,
magically
Author: larry
Date: Sat Apr 22 11:24:56 2006
New Revision: 8910
Modified:
doc/trunk/design/syn/S02.pod
doc/trunk/design/syn/S03.pod
doc/trunk/design/syn/S05.pod
Log:
Fixes from Daniel and Markus.
Various clarifications on string positions vs Str and Buf types
Broke down and added the as
Audrey Tang wrote:
> Hm, Perl 6 actually has two different ways of putting Capture to some
> Code object... Following yesterday's P6AST draft I'll call them Call and
> Apply respectively:
>
> moose($obj: 1, 2); # this is Call
> &moose.($obj: 1, 2); # this is Apply
>
> elk(named
Dave Whipp wrote:
> Also, I'm a bit confused By the idea that the invocant is obtained by a
> scalar dereference, because I know that arrays and hashes can be
> invocants, too. E.g. @a.pop. So, If I do:
>
> my $args = \(@a:);
> my $b = $$args; # @a as a scalar
> my @c = @$args; # empty l
Author: larry
Date: Sat Apr 22 17:21:32 2006
New Revision: 8913
Modified:
doc/trunk/design/syn/S03.pod
doc/trunk/design/syn/S05.pod
doc/trunk/design/syn/S06.pod
doc/trunk/design/syn/S11.pod
Log:
Killed postfix ... dead.
Generalized "Whatever" from subscripts to any MMD op that accepts
Given the recent explosion of svn commits in the synopses, and the fact that
the versions of the synopses on the dev.perl.org/perl6 site are lagging a
bit, would it make sense to add a link to the svn site to the Synopses page?
This week, when I wanted to read the cumulative changes to some of
On Sat, Apr 22, 2006 at 05:52:31PM +0800, Audrey Tang wrote:
: During my S03 cleanup today, I noticed that because *$fh and **$fh
: interpolates into the current argument list, it's always the same as
: =$fh under list context. So I wrote this paragraph:
:
: [Conjectural: File handles interpolate
11 matches
Mail list logo
