New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
globals in !UNIT_START set up too late, or statements executed too early #697
Comments
From @chrisdolanIf you include statements in the body of a package, class, etc. ../../parrot perl6.pbc -e 'say "(", @*ARGS, ")";' f g h ../../parrot perl6.pbc -e 'package Foo { say "(", @*ARGS, ")"; }' f g h ../../parrot perl6.pbc -e 'package Foo { sub run() { say "(", @*ARGS, |
From @cokeOn Fri Feb 13 20:46:31 2009, chris@chrisdolan.net wrote:
... Now a /different/ two of these work: $ ./perl6 -e 'say "(", @*ARGS, ")";' f g h -- |
The RT System itself - Status changed from 'new' to 'open' |
From @cokeOn Tue Jul 27 18:07:28 2010, coke wrote:
jnthn++ points out that this last failure is correct. This should be written: $ ./perl6 -e 'package Foo { our sub run() { say "(", @*ARGS, ")"; } }; Foo::run()' f g h which works. Assigning to moritz for spectesting. -- |
From @tadzikOn Tue Jul 27 18:12:24 2010, coke wrote:
Got some work of moritz's back. Test added in |
@jnthn - Status changed from 'open' to 'resolved' |
Migrated from rt.perl.org#63226 (status was 'resolved')
Searchable as RT63226$
The text was updated successfully, but these errors were encountered: