Author: lwall
Date: 2009-01-30 08:12:14 +0100 (Fri, 30 Jan 2009)
New Revision: 25122
Modified:
docs/Perl6/Spec/S02-bits.pod
Log:
[S02] random clarifications
Modified: docs/Perl6/Spec/S02-bits.pod
===
--- docs/Perl6/Spec/S02-bits.
Author: lwall
Date: 2009-01-30 08:11:23 +0100 (Fri, 30 Jan 2009)
New Revision: 25121
Modified:
docs/Perl6/Spec/S19-commandline.pod
Log:
[S19] more comments
Modified: docs/Perl6/Spec/S19-commandline.pod
===
--- docs/Perl6/Spec/S19
[STD, S03] slaughter of the LTM metatokens
This cleans up the metaop scene quite a bit. Bravo!
I went through STD.pm with a fine tooth comb again, to extract what
I'd say about which operators were allowed to be meta'd by each given
metaop:
(The notation "foo --> bar" means, takes an ope
On Thursday 29 January 2009 02:14:23 Jonathan Worthington wrote:
> > Can you show some example PIR code that should work?
>
> Ah, yes, sorry...
>
> .sub 'main'
> $S0 = 'foo'
> example('foo'=>42) # works
> # example($S0=>42) # what I want to work also
> .end
>
> .sub 'example'
> .pa
Author: lwall
Date: 2009-01-29 21:32:51 +0100 (Thu, 29 Jan 2009)
New Revision: 25113
Modified:
docs/Perl6/Spec/S03-operators.pod
src/perl6/STD.pm
Log:
[STD, S03] slaughter of the LTM metatokens
STD now runs considerably faster
Freed from LTM, metaoperators may now be nested arbitrarily deep
Author: bernhard
Date: Thu Jan 29 09:30:19 2009
New Revision: 36147
Modified:
trunk/docs/pdds/pdd28_strings.pod
Log:
[codingstd] pdd_format.t
Modified: trunk/docs/pdds/pdd28_strings.pod
==
--- trunk/docs/pdds/pdd28_s
On Thu, Jan 29, 2009 at 09:00:06AM +0100, Eirik Berg Hanssen wrote:
: Jon Lang writes:
:
: > So "$a -<=> $b" is equivalent to "$b <=> $a", not "-($a <=> $b)". OK.
: > I'd suggest choosing a better character for the meta-operator (one
: > that conveys the meaning of reversal of order rather than
chromatic wrote:
On Wednesday 28 January 2009 05:43:08 jn...@jnthn.net via RT wrote:
I figured this would be easy to fix, but it's not. Basically, because
for infix:=> we could have any complex expression that generates a key
on the RHS, and Parrot does not allow us to pass named arguments w
On Wednesday 28 January 2009 05:43:08 jn...@jnthn.net via RT wrote:
> I figured this would be easy to fix, but it's not. Basically, because
> for infix:=> we could have any complex expression that generates a key
> on the RHS, and Parrot does not allow us to pass named arguments where
> the name i
I took the quotation marks to indicate an intentional
misspelling/coinage: "perl" + "prelude" = "perlude".
On 1/29/09, Moritz Lenz wrote:
> pugs-comm...@feather.perl6.nl wrote:
>> +PERL# Lexical symbols in the standard "perlude"
>
> Did you mean "prelude" instead?
>
> Moritz
>
--
Jon Lang writes:
> So "$a -<=> $b" is equivalent to "$b <=> $a", not "-($a <=> $b)". OK.
> I'd suggest choosing a better character for the meta-operator (one
> that conveys the meaning of reversal of order rather than opposite
> value); but I don't think that there is one.
A transposition of
11 matches
Mail list logo
