Hi, there~
Perl 5 uses the "\ddd" notation to index characters by octal numbers
(e.g. \187 and \13). Now that Perl 6 has the shiny new \o and \o[]
notations, we probably need to outlaw the legacy stuff explicitly in
S02 since we have the assumption that everything not mentioned in the
Synopses is
Hello~
Here is a snippet from the Pugs test suite:
{
my $ret = eval 'do 42';
ok(!$ret, 'do EXPR should not work', :todo);
# XXX or should it? Feels weird...
}
which motivated me to create the following patch for S04:
Index: D:/projects/Perl6-Syn/S04.pod
David Green writes:
> I guess my problem is that [1,2] *feels* like it should === [1,2].
> You can explain that there's this mutable object stuff going on, and I
> can follow that (sort of...), but it seems like an implementation
> detail leaking out.
The currently defined behaviour seems intuiti
David Green writes:
> On 8/13/06, Smylers wrote:
>
> > Please could the proponets of the various behaviours being discussed
> > here share a few more concrete examples ...
>
> OK,
Thanks for that. In summary, if I've understood you correctly, it's
that:
=:= two aliases to the same actual v
Author: larry
Date: Tue Aug 15 08:40:59 2006
New Revision: 10969
Modified:
doc/trunk/design/syn/S02.pod
Log:
Explicitly outlawed \123 and the like.
Modified: doc/trunk/design/syn/S02.pod
==
--- doc/trunk/design/syn/S
Author: larry
Date: Tue Aug 15 08:41:37 2006
New Revision: 10970
Modified:
doc/trunk/design/syn/S02.pod
Log:
typo
Modified: doc/trunk/design/syn/S02.pod
==
--- doc/trunk/design/syn/S02.pod(original)
+++ doc/t
Author: larry
Date: Tue Aug 15 08:52:46 2006
New Revision: 10971
Modified:
doc/trunk/design/syn/S04.pod
Log:
Clarifications on C with bare expression.
Modified: doc/trunk/design/syn/S04.pod
==
--- doc/trunk/design/sy
David Green schreef:
> ===
> ...is equality-of-contents, basically meaning that the things you're
> comparing contain the same [...] values.
How about strings; are normalized copies used with the === ?
http://www.unicode.org/faq/normalization.html
http://www.unicode.org/notes/tn5/
--
Affijn, R
On 8/14/06, Smylers wrote:
David Green writes:
Thanks for that. In summary, if I've understood you correctly, it's that:
=:= two aliases to the same actual variable
=== one variable contains a copy of the other's actual contents
eqv both contain contents which represent the same thing
On 8/14/06, Smylers wrote:
David Green writes:
I guess my problem is that [1,2] *feels* like it should === [1,2].
You can explain that there's this mutable object stuff going on, and I
can follow that (sort of...), but it seems like an implementation
detail leaking out.
The currently defin
It seems to me that there is some confusion being given in this
thread and the most recent parts of its predecessor (which can lead
to FUD in the wrong hands), so I'll briefly try to clear it up, as I
would like to think I understand the issues.
At 2:51 PM -0600 8/15/06, David Green wrote:
On
11 matches
Mail list logo
