[perl #76400] [BUG] Null PMC access when doing 'say $foo::' (which shouldn't even parse) in Rakudo

2014-10-28 Thread Christian Bartolomaeus via RT
We're back to the behaviour from 2011: $ perl6 -e '$foo:: = 42; say $foo::' 42 $ perl6-m -e 'say $foo::' (Any) But I wonder whether this is really correct. The subject states that 'say $foo::' should not parse and TimToadys remarks sound likewise: > std 31559: OUTPUT«ok 00:01 111m␤» > I didn

[perl #76400] [BUG] Null PMC access when doing 'say $foo::' (which shouldn't even parse) in Rakudo

2013-11-12 Thread Will Coleda via RT
On Sat Oct 08 13:03:15 2011, coke wrote: > On Tue Jul 06 09:19:10 2010, masak wrote: > > std 31559: OUTPUT«ok 00:01 111m␤» > > I didn't expect that to work :) > > std bug. > > * TimToady bug > > I'm not entirely sure how it parsed... > > oh, morename allows a final :: component, but that's not

[perl #76400] [BUG] Null PMC access when doing 'say $foo::' (which shouldn't even parse) in Rakudo

2011-10-08 Thread Will Coleda via RT
On Tue Jul 06 09:19:10 2010, masak wrote: > std 31559: OUTPUT«ok 00:01 111m␤» > I didn't expect that to work :) > std bug. > * TimToady bug > I'm not entirely sure how it parsed... > oh, morename allows a final :: component, but that's not > quite what you want here > std: $defeat-the-name-ch

[perl #76400] [BUG] Null PMC access when doing 'say $foo::' (which shouldn't even parse) in Rakudo

2010-07-08 Thread Carl Mäsak
# New Ticket Created by "Carl Mäsak" # Please include the string: [perl #76400] # in the subject line of all future correspondence about this issue. # http://rt.perl.org/rt3/Ticket/Display.html?id=76400 > std 31559: OUTPUT«ok 00:01 111m␤» I didn't expect that to work :) std bug. * TimToady