Fixed in 754664ed54aea24f9c9162002b6e68aadd311412.
On Thu, 28 Apr 2016 07:06:42 -0700, gfldex wrote:
> enum Bits ( (('Bit-' X~ 1..8) Z=> (1, 2, 4 ... 256)) ); dd Bits.enums;
> # OUTPUT«{"Bit-1\t1" => 0, "Bit-2\t2" => 1, "Bit-3\t4" => 2, "Bit-
> 4\t8" => 3, "Bit-5\t16" => 4, "Bit-6\t32" => 5,
Fixed in 754664ed54aea24f9c9162002b6e68aadd311412.
On Wed, 08 Oct 2014 05:20:07 -0700, timo wrote:
> compare:
>
> > perl6-m -e 'enum Bug ("foo" => -1, "A", "B"); say +A; say +B;'
> > 1
> > 2
>
> and:
>
> > perl6-m -e 'enum Bug (foo => -1, "A", "B"); say +A; say +B;'
> > 0
> > 1
>
>
Fixed in 754664ed54aea24f9c9162002b6e68aadd311412.
Note however, that there's a braino above, since the 'my' is initialized after
the value is needed. So the fix is to warn about an empty variable, not to
make it work. (It does work if you make it a constant, or put the my inside a
BEGIN.)
Actually, the Z=> misbehavior is already called out in #128017.
On Tue, 28 Nov 2017 00:04:05 -0800, larry wrote:
> This also showed up when doing things like:
> enum Foo ( Z=> 1,2,3);
>
> Fixed in d9021cf16e7df051c5e17c33919c9bde44c5e0db but tests needed.
>
>
> On Mon, 07 Nov 2016 11:37:06
Actually, the Z=> misbehavior is already called out in #128017.
On Tue, 28 Nov 2017 00:04:05 -0800, larry wrote:
> This also showed up when doing things like:
> enum Foo ( Z=> 1,2,3);
>
> Fixed in d9021cf16e7df051c5e17c33919c9bde44c5e0db but tests needed.
>
>
> On Mon, 07 Nov 2016 11:37:06
This also showed up when doing things like:
enum Foo ( Z=> 1,2,3);
Fixed in d9021cf16e7df051c5e17c33919c9bde44c5e0db but tests needed.
On Mon, 07 Nov 2016 11:37:06 -0800, FROGGS.de wrote:
> m: enum Foo ( A => 42, 'B', 'C', 'D' ); say +B
> rakudo-moar e10f76: OUTPUT«43»
>
> m: enum Foo (
Yes, as noted above, this is a dup of rejected ('better docs needed', really)
ticket #130562.
Yes, as noted above, this is a dup of rejected ('better docs needed', really)
ticket #130562.
Only *@foo and *%foo are slurpy, as in "slurping up the rest of the arguments.
But the term "variadic" refers to all optional arguments including named ones,
so it would be incorrect to call those "slurpy", because they don't. It's like
the difference between * and ? in regex.
Larry
On Fri,
Only *@foo and *%foo are slurpy, as in "slurping up the rest of the arguments.
But the term "variadic" refers to all optional arguments including named ones,
so it would be incorrect to call those "slurpy", because they don't. It's like
the difference between * and ? in regex.
Larry
On Fri,
We now warn on the ambiguity of >> or » when used where it could easily be
intended as either a hyper or the quotewords terminator. While we could, in
theory, do some lookahead to try to suppress this warning in some cases, it
will be brittle in the face of languages that mutate the postfix
On Fri, 09 Jan 2015 10:59:08 -0800, masak wrote:
> m: say :256["☺".ords]
> rakudo-moar c5dcdf: OUTPUT«9786»
> m: say :256[0x263a]
> rakudo-moar c5dcdf: OUTPUT«9786»
> seems we could use a check there...
> m: say :256[256,256]
> rakudo-moar c5dcdf: OUTPUT«65792»
> * masak submits
On Sat, Oct 15, 2016 at 09:59:01PM +0200, Timo Paulssen wrote:
: Actually, I just tested the code and on my machine it always outputs
: "test". The only difference between uncommenting "say 'run'" is that
: it'll output "run" once at the end - or not.
:
: So now I'm wondering what i did
On Sat, Oct 15, 2016 at 09:59:01PM +0200, Timo Paulssen wrote:
: Actually, I just tested the code and on my machine it always outputs
: "test". The only difference between uncommenting "say 'run'" is that
: it'll output "run" once at the end - or not.
:
: So now I'm wondering what i did
On Fri, Sep 23, 2016 at 11:42:20PM -0700, Itsuki Toyota wrote:
: # New Ticket Created by Itsuki Toyota
: # Please include the string: [perl #129346]
: # in the subject line of all future correspondence about this issue.
: # https://rt.perl.org/Ticket/Display.html?id=129346 >
:
:
: See the
On Fri, Sep 23, 2016 at 11:42:20PM -0700, Itsuki Toyota wrote:
: # New Ticket Created by Itsuki Toyota
: # Please include the string: [perl #129346]
: # in the subject line of all future correspondence about this issue.
: # https://rt.perl.org/Ticket/Display.html?id=129346 >
:
:
: See the
Rakudo now gives a decent error (X::Syntax::Signature::InvocantNotAllowed), and
there's even a test for it.
I'm fine with the rakudo behavior here.
The chance of someone using $. inside a regex and meaning what it means in Perl
5 is minimal. Best to just leave this as a "can never match".
Test was bogus. Replaced with test that assumes Empty semantics on next.
test fixed in 06f9c5d010986a7a8dde907971e25985e8ba4601
The code generator in nqp for char ranges was incorrectly using ordat and
ordfirst to find the character to compare, which throw away information on
synthetic characters. We now use the getcp_s instruction instead, which leaves
synthetics negative, so that they drop out of the character range
Binding of the map routine internally now requires list elements to bind as
Pair, which improves the error message.
(The alternate approach of inserting a CATCH into the map closure could in
theory produce an even better message, but it appeared to slow things down more
than the Pair binding
Some method calls were not properly sunk as a final statement in a loop.
Fix in 977797fa401856e5310155f13469b7e6ff5f620a
Test in bc8fa4fd8d449573eb6001b5f43f8890f65b9196
The unwanted() routine needed to add an explicit sink to certain methods found
in a block-final Want node. (Method calls for dispatch:<.=> and Pair.new are
exempt, however. In the case of .=, it is 'nosink' because it's essentially
going to cause a side effect anyway, and doing it twice tends
The repeat and loop constructs weren't properly self-sinking at statementlist
level.
Fixed in 589061eac14f2847e2c4b401d2ff2eb30c62675e
Test in cbbff3ba0f1120fe7dfded0a980f9b73263f0868
The repeat and loop constructs were not properly sinking themselves at
statementlist level.
Fixed in 589061eac14f2847e2c4b401d2ff2eb30c62675e
Untodo'd existing test.
We now examine the preceding character, and if it's a closing brace, suggest
use of whitespace before curlies taken as a hash subscript.
Fixed in 7ec824e52ab5b285cda47179e6f41e452d870762
We've split the non-associative exceptions into the base class,
X::Syntax::NonAssociative, with a subclass off X::Syntax::NonListAssociative.
nqp's EXPR now calls a different method to fail list associativity, and rakudo
provides the alternate method to get the appropriate message.
nqp fix in
The onearg form of reduce wasn't correctly marking wantedness of either the
operator or the argument.
Fixed in fc28b67185d711cf8e4b3f9e6987e1ceee34e37b.
(We don't test sink warnings currenlty.)
The logical ops andthen, notandthen, and orelse were not propagating wantedness
to their thunky args.
Fixed in 7ba6dbfae97f5ff9398336e49267d51606512df9.
Note that we don't generally test sink warnings currently.
Not A Bug.
LTM requires it to recognize => over = inside, and then you're missing a >.
Looking at it from the other direction, thinking that it will find the >> on
the end and then back up to isolate the = is a subtle mental trap of two-pass
parsing, which is typically forbidden in Perl 6.
Now says: Virtual method call $.foo may not be used on partially constructed
object (maybe you mean $!foo for direct attribute access here?)
Fix in 5a69da88b9b16f916125add8f89aff68113a9877
Fix in 386905f6f62f9fa3525c887a8a86fa48b22b4b35 and
37e742f0bb6f36f1a9d9a5f947c5c0de15d236c2
Test in ba521fa8101f3114c87ec1a295707cb68b5b
Dup of #127013.
Tests for this particular ticket in a8bbde8fa06d5d55bc6d5879a0c84a669d7f0481
Dup of #127013, see fix there.
Fixed in 02588190492349fabde00c5a15b873ea61a9333e
Tested in 2f126a3ab7d0991767ca84c562b8f3ae97b25c4e
There are no tests there for with or whenever, but those did not appear to
misbehave when I tried them on the command line. Feel free to add more tests
for those.
Fixed in 091ee7507464595e7712f4ae911d95d467e5281b
Tests in 8b97aa4f6191affdd91da78607eca4ae6dc73b11
A new restricted dialect of regex is implemented in
28ab83f947b4899a4f8698eee5bc056742f356f1 and
19d84be0066978f616ace6fa9f506e742161a378
Tests in 1becd7c9b456b707a14bfba40d672ec28945f199
Fixed, along with all the other metaops, in:
1e1556b1a25bc4c73a505fdd249d4179ffc813de
0a2303c0f6a2a3782fecb13db1523cb5442467de
67202d697d3fe48b800e95262bebe6da17bfcf49
e2e23fb8853808839884f23a0b8aa91f458fd310
97ef742f350e84dae275ed2dc9d453795f057dba
6516930c86d6ff4296ee8699a64eb1315eed2583
Tests:
The purpose of stubbing is to guarantee the public interface is complete, and
since the public interface of attributes is entirely via accessors, it suffices
to merely stub the accessor, and leave it up to the class whether it should
implement that name via an explicit method or an attribute
Fixed for moarvm with nqp patch 2661d275d2427a1d3ceeed0f5ac9fb1494e4e122
(jvm not patched yet)
nqp/jvm fix in f17e8c56ff171377999e468fe65e75a3ba807a4b
tests in aef8ea1df4beed8f69b6ecb80784e78c6e2c6680
Matching only the final match is not desirable, in my opinion. It should match
the string traversed by all the matches in $0, including intervening
separators, if any. The problem is that ~$0 has spaces interpolated, which will
match only if the separators happen to be a single space, so there
Fixed in 9e4902f772b0e86fe96771b22039aaf1a57fae34
Fixed in 36a35142a0b7dadd65a5b09bcba7f460845ae3e9
Tests in 2ccb4443d61efd053419239203106e5636b021ce and
7cd9f97ccdad6299c3b6dc4d4b071c6580c0b66c
On Mon Oct 19 07:02:44 2015, elizabeth wrote:
> Fixed with a31cc91a0d604a8a74529 . Tests are still needed
>
> > On 19 Oct 2015, at 03:42, Carsten Hartenfels (via RT) > follo...@perl.org> wrote:
> >
> > # New Ticket Created by Carsten Hartenfels
> > # Please include the string: [perl #126394]
On Sat Oct 10 08:33:13 2015, FROGGS.de wrote:
> say class { has Int $.foo is default(0) }.new.foo
> rakudo-moar 025ec1: OUTPUT«(Int)»
>
> class Foo { has Int $.foo is default(0) }; say Foo.new.foo
> rakudo-moar 025ec1: OUTPUT«(Int)»
>
> I would expect that foo is zero in both cases.
Even less
Fixed with 23248109c9c93db2774fcc9ce0c849a73a01fdad
Tested with f8c0844fbffeac6022603cda8bfbc4f1f35e9a57
On Wed Oct 14 09:46:18 2015, larry wrote:
> 09:39 < TimToady> HLL::Compiler is very confused about what is the language
> name/version vs compiler name/version, and this shows up in both -v and -V
> 09:40 < TimToady> "This is perl6 version 2015.09-373-g254c1a8"
> 09:42 < TimToady> should be more
nqp fix in a79e4abbe60d28f59b451416e7946ee433db7199
rakudo fix in 091637fd5ace48a0835fc8af786f2caa372381cf
roast fix in dc3e1335232bb617b42d335ddbcc42be0a9dedaa
Statement modifiers now behave as terminators. Tests in
6fa03d9816b1613762f12def4bbc556dbb5fb3d5
Whoops, posted the wrong examples. These actually show the difficulty:
> p6 'say() <== map { $_ * 2 } <== 1...10'
(2 4 6 8 10 12 14 16 18 20)
> p6 'say() <== map { $_ * 2 },0 <== 1...10'
(0 20)
So this really looks like an insidious case of accidental one-arg semantics.
This works now, due to the precedence changes associated with adding the dot
infix operator.
Mu ~~ 0 now works but will always return False, since we don't want people to
start using Mu as a numeric semipredicate.
Don't need this, using the Top or other rule name is sufficient.
Since the sort is stable, I believe it suffices simply to sort on the .to
instead of the .from.
Larry
On Mon, Jun 15, 2009 at 12:17:41PM -0700, Patrick R. Michaud via RT wrote:
: A related question may be: what should the following produce?
:
: 1..4 :by(0)
Same as 1 xx *, I suppose. I don't know if the range would be smart
enough to report itself as an infinite iterator, so a mostly eager
On Mon, Jun 15, 2009 at 12:17:41PM -0700, Patrick R. Michaud via RT wrote:
: More to the point, if you want to cycle through a range of codepoints,
: you probably want:
:
: map { .chr }, 44032..45208;
Well, almost certainly you'd want it in hex, but yes.
: I agree that the string form of
We now spec a simple temporization (doesn't even have to be implemented
using temp) for topicalizing statement modifiers. See latest S04.
Larry
On Thu, May 21, 2009 at 07:20:57PM +0200, Gianni Ceccarelli wrote:
: On 2009-05-21 Larry Wall la...@wall.org wrote:
: : dakkar rakudo: sub infix:R($a,$b) { $a ~ '-' ~ $b }; sub
: : infix:RR($a,$b) { $a ~ '_' ~ $b }; say 'x' R 'y'; say 'x' RR 'y';
: : p6eval rakudo e6b463: OUTPUT«x-yx_y
On Thu, May 21, 2009 at 02:56:23AM -0700, Carl Mäsak wrote:
: # New Ticket Created by Carl Mäsak
: # Please include the string: [perl #65878]
: # in the subject line of all future correspondence about this issue.
: # URL: http://rt.perl.org/rt3/Ticket/Display.html?id=65878
:
:
: dakkar
On Tue, May 19, 2009 at 10:24:41AM -0500, Patrick R. Michaud wrote:
: On Tue, May 19, 2009 at 12:30:53AM -0700, Ahmad Zawawi wrote:
: Given the following:
:
: 1.say;
: =begin pod
: =end pod1
: 2.say;
:
: The output is only 1 but should be 1\n2 or at least a runtime
: error message for
I should also point out that a lot of the brainstorming and thrashing
out actually happens on IRC, specifically #perl6 at irc.freenode.net.
(Though the s2n ratio is highly variable there, as on any IRC channel.)
It is logged at http://irclog.perlgeek.de/perl6/today. There is
usually someone
On Tue, Feb 10, 2009 at 12:14:35PM -0800, Carl Mäsak wrote:
: # New Ticket Created by Carl Mäsak
: # Please include the string: [perl #63146]
: # in the subject line of all future correspondence about this issue.
: # URL: http://rt.perl.org/rt3/Ticket/Display.html?id=63146
:
:
: TimToady my
On Thu, Jan 15, 2009 at 09:58:12AM -0600, Patrick R. Michaud wrote:
: On Wed, Jan 14, 2009 at 10:02:21PM -0800, Carl Mäsak via RT wrote:
: On Wed Jan 14 22:00:33 2009, masak wrote:
: TimToady rakudo: my $t = 5; say $t.i
: p6eval rakudo 35576: OUTPUT«Method 'i' not found for invocant of
:
On Tue, Jan 06, 2009 at 08:39:00PM -0600, Patrick R. Michaud wrote:
: On Tue, Jan 06, 2009 at 01:50:06PM -0800, Dave Whipp wrote:
:
: S16 requires that say (and print) when called with no args should
: be a compile-time error. Rakudo accepts it with no error.
:
: Since S16 has been in an
On Fri, Dec 19, 2008 at 10:04:34AM +0100, mor...@casella.faui2k3.org wrote:
: # New Ticket Created by Carl Mäsak
: # Please include the string: [perl #61494]
: # in the subject line of all future correspondence about this issue.
: # URL: http://rt.perl.org/rt3/Ticket/Display.html?id=61494
On Wed, Nov 26, 2008 at 08:54:50AM +0100, Moritz Lenz wrote:
:
:
: Patrick R. Michaud wrote:
: Currently Rakudo is treating [EMAIL PROTECTED] as though it's
: prefix:^ on a List, which S03 says
:
: If [prefix:^ is] applied to a list, it generates a
: multidimensional set of
On Thu, Nov 20, 2008 at 04:31:22PM +0100, Carl Mäsak wrote:
: Mark ():
: I think the most sensible thing is to be consistent. sgn() fails for
: non-real input as long as sqrt() returns NaN for negative input.
: Change the latter behavior (via a pragma or whatever) so that sqrt()
: returns
On Sun, Oct 05, 2008 at 08:03:43PM +0200, Moritz Lenz wrote:
: Patrick R. Michaud wrote:
: On Fri, Oct 03, 2008 at 10:02:56AM +0200, [EMAIL PROTECTED] wrote:
: +#?rakudo skip ',='
: +#?DOES 2
: +{
: +my @a = 1, 2;
: +is (@a ,= 3, 4).join('|'), '1|2|3|4', ',= on lists works the same
On Thu, Aug 14, 2008 at 02:32:29AM -0500, Patrick R. Michaud wrote:
: AFAICT, according to the grammar it's valid standard Perl 6 syntax.
At least in pugs, 42[0] is legal, and produces the value 42, on
the theory that anything can be considered a list of 1 item, and
if you use something as a
On Fri, Jul 18, 2008 at 05:53:17PM +0200, Carl Mäsak wrote:
: Here's a 1-line patch that fixes nothing, pmichaud++.
Note that nothing is now unspecced. :)
Larry
On Mon, Jul 07, 2008 at 07:16:05PM -0700, Patrick R. Michaud via RT wrote:
: Note however that TimToady on #perl6 speculated [1] that an empty return
: should return the Object prototype. I'm not sure the answer was
: resolved completely in that thread, however, so we'll go with returning
:
On Mon, Jul 07, 2008 at 11:43:56PM -0500, Patrick R. Michaud wrote:
: On Mon, Jul 07, 2008 at 08:18:36PM -0700, Larry Wall wrote:
: On Mon, Jul 07, 2008 at 07:16:05PM -0700, Patrick R. Michaud via RT wrote:
: : Note however that TimToady on #perl6 speculated [1] that an empty return
: : should
On Mon, Jul 07, 2008 at 10:09:37PM -0700, Larry Wall wrote:
: So
:
: $x = nothing(); # = []
: @x = nothing(); # = ()
: %x = nothing(); # = ()
: if nothing() {...}# always false
: $x = nothing()[0] # Subscript out of range
On Thu, Jun 26, 2008 at 12:45:39PM -0400, Mark J. Reed wrote:
: Moritz Lenz 3.14 would be a Rat or a Float or whatever
:
: That's a good question, actually. Does the literal 3.14 get turned
: into a Float or a Rat? Float is probably simplest, and matches what
: e.g. Lisp does, but you could
On Thu, Jun 05, 2008 at 11:04:52AM -0500, Patrick R. Michaud wrote:
: This message is looking for a clarification/confirmation.
: S12:207 says:
:
: To call an ordinary method with ordinary method-dispatch semantics,
: use either the dot notation or indirect object notation:
:
:
On the theory that a List is just a Capture that happens to contain
only positionals, I'd say Lists should try to behave like Arrays
when used as one. The only counterargument would be if it forces
unnecessary mutation of otherwise immutable values, but that doesn't
seem to be required for
On Wed, Jan 30, 2008 at 04:08:04PM +0100, Moritz Lenz wrote:
: About half a year ago I posted my idea of a program that explains Perl 6
: syntax:
:
: http://www.nntp.perl.org/group/perl.perl6.users/2007/07/msg621.html
:
: Differing from my first post I know think that the best idea is to
:
On Wed, Jan 30, 2008 at 07:47:18PM +0100, Moritz Lenz wrote:
: particle++ told me to try --target=parse instead, and that's pretty much
: verbose and all I should ever need ;-)
Hmm, yes, but *only* if that switch merely augments information without
destroying information, and doesn't otherwise
On Wed, Jan 16, 2008 at 05:38:32AM -0600, Patrick R. Michaud wrote:
: Nice. What about the cases where a test file defines its own local
: wrapper functions to is, isnt, like, etc.? For example, Pugs'
: t/builtins/math/sqrt.t has:
:
: sub is_approx (Num $is, Num $expected, Str $descr) {
:
On Wed, Jan 16, 2008 at 09:18:17AM -0800, Larry Wall wrote:
: We could reserve all the is_* isnt_* ok_* names for that, I suppose.
I've gone ahead and done that. Let me also reiterate here in public
the basic underlying premise that fudge is only for fudging the
tests, and a truly passing test
On Sun, Jan 13, 2008 at 11:22:44PM -0600, Patrick R. Michaud wrote:
: On Sun, Jan 13, 2008 at 11:35:17PM +0100, Cosimo Streppone wrote:
: - Is [1] the correct way of declaring todo tests?
:What's the equivalent in new compiler directives
:of `:todofeature', `:todobug', and ':todo'?
: [1]
On Mon, Sep 03, 2007 at 01:01:28PM +0200, Wolfgang Laun wrote:
: The pugscode page http://www.pugscode.org/ contains the hint
:
: Periodic releases will appear on CPAN under the Perl6-Pugs
: http://search.cpan.org/dist/Perl6-Pugs/ namespace.
Well, hey, it doesn't specify the time period... :)
Looks like some kind of resource exhaustion or lockup, possibly with
the embedded/tunneled Perl 5, but it's hard to guess without more
information like OS, locale, etc. most of which would be supplied by:
pugs -V
perl -V
env
If you provide that sort of info, we can compare with our
On Wed, Aug 23, 2006 at 05:01:43PM -0400, Mark J. Reed wrote:
: Sorry if this is a known question, but I didn't see it mentioned in the
: recent archive or FAQ.
:
: for ($a, $b) { $_ = ... }
:
: gives me a Can't modify constant item: VRef Scalar.
Which is correct as the default.
: Making it
On Thu, Aug 24, 2006 at 02:29:04PM -0400, Mark J. Reed wrote:
: Is there a repository of current known bugs with pugs, like there is
: with Parrot? I'm just starting and don't want to point out things
: that are already known.
The pugs idea of reality is that a bug doesn't exist unless there's a
On Thu, Aug 24, 2006 at 03:11:10PM -0400, Mark J. Reed wrote:
: On 8/24/06, Larry Wall [EMAIL PROTECTED] wrote:
: On Wed, Aug 23, 2006 at 05:01:43PM -0400, Mark J. Reed wrote:
: : Sorry if this is a known question, but I didn't see it mentioned in the
: : recent archive or FAQ.
: :
: : for ($a, $b
[Time to stop spamming multiple lists. Followups to p6c for bikeshedding.]
On Sat, Aug 12, 2006 at 10:30:22AM +0300, Gaal Yahas wrote:
: On Sat, Aug 12, 2006 at 02:06:27PM +0800, Agent Zhang wrote:
: is $got, $expected, todo :pugs6.2.13, :p6p50.110;
:
: Happily, Audrey has already
On Fri, Jun 16, 2006 at 10:51:24PM -0500, John M. Dlugosz wrote:
: Anyway, as passionate as I was about resumption, or at least making it
: not impossible to implement resumption, at the next ANSI meeting the
: terminate-only camp made compelling arguments.
Well, interestingly, I used to be in
On Wed, Jun 14, 2006 at 08:59:02PM -0700, Chip Salzenberg wrote:
: Are Parrot exceptions now, in fact, resumable? If they are, is that
: important? Is anyone actually resuming execution after exception handlers
: are called? I think we _can_ keep resumability, but I'm not sure I want us
: to,
On Wed, Apr 19, 2006 at 10:08:29PM +0800, Audrey Tang wrote:
: Not sure if this is p6l or p6c... Fallback to the latter. :)
:
: In this line:
:
:[Dog ::T $ ($x) where 1, *$, [EMAIL PROTECTED] := moose();
:
: the left hand side is probably not a valid Perl 6 expression, yet
: according to
After some discussion on IRC, we have all declarators implying a signature
syntax, either with parens for full sig or without for a limited one arg
syntax:
my Int $x = 1;
my (Int $x where Odd, Dog $spot = fido()) := (1,$lassie);
The sigil or the parens still control the context of the
say $::You can already do that!;
Larry
On Tue, Feb 07, 2006 at 03:28:05PM -0800, Larry Wall wrote:
: say $::You can already do that!;
Or you can use a symbolic ref with a constant string:
$::('x y');
The compiler knows it's a constant. And it's even implemented in Pugs.
But my thinking on the :: form is that it derives from
On Wed, Feb 08, 2006 at 12:26:52AM +, Luke Palmer wrote:
: On 2/7/06, Larry Wall [EMAIL PROTECTED] wrote:
: $MY::{'x y'}
: $MY::x y # same thing
: MY::$x y # same thing
:
: Er, aren't we obscuring the meaning of a little bit here? I would
: think
On Tue, Feb 07, 2006 at 03:54:07PM -0800, Larry Wall wrote:
: On Tue, Feb 07, 2006 at 03:28:05PM -0800, Larry Wall wrote:
: : say $::You can already do that!;
:
: Or you can use a symbolic ref with a constant string:
:
: $::('x y');
:
: The compiler knows it's a constant. And it's even
After a little more cleanup, S06 now reads:
=head2 Macros
Macros are functions or operators that are called by the compiler as
soon as their arguments are parsed (if not sooner). The syntactic
effect of a macro declaration or importation is always lexically
scoped, even if
On Thu, Feb 02, 2006 at 10:58:39PM -0500, Uri Guttman wrote:
: LW == Larry Wall [EMAIL PROTECTED] writes:
:
: LW pugs -V:
:
: LW This is Perl6 User's Golfing System, version 6.2.11, February 1,
: LW 2005 (r8945) built for i386-linux-thread-multi
:
:
: not that this has
Here's results of r8894 on up-to-date Fedora Core 4 with embparrot
r11392. Other the usual embparrot rules breakage, is looking pretty
clean here even with bleadparrot. All the failures below look like
rules coredumps to me, including the undef.t one.
Larry
Failed Test
1 - 100 of 132 matches
Mail list logo
