Skip to content
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

Cannot declare fixed-sized or explicitly autoextending arrays #1142

Closed
p6rt opened this issue Jul 15, 2009 · 4 comments
Closed

Cannot declare fixed-sized or explicitly autoextending arrays #1142

p6rt opened this issue Jul 15, 2009 · 4 comments

Comments

@p6rt
Copy link

p6rt commented Jul 15, 2009

Migrated from rt.perl.org#67600 (status was 'resolved')

Searchable as RT67600$

@p6rt
Copy link
Author

p6rt commented Jul 15, 2009

From minimiscience@gmail.com

Rakudo is unable to parse any of the following declarations​:

  my @​a[5];
  my @​b[5;4];
  my @​c[*];
  my @​d[5;*];
  my @​e[*;4];
  my @​f[*;*];

(This seems like a bug that would have already been reported, but I
couldn't find any references to it in the request tracker.)

This problem was observed on Rakudo Perl #​18 ("Pittsburgh") with
revision 39599 of Parrot on Mac OS X 10.5.6.

@p6rt
Copy link
Author

p6rt commented Aug 3, 2010

From @bbkr

All cases can be declared on * release

$ perl6

my @​a[5];

my @​b[5;4];

my @​c[*];

my @​d[5;*];

my @​e[*;4];

my @​f[*;*];

$ perl6 -v

This is Rakudo Perl 6, version 2010.07-47-g9fd5eaa built on parrot 2.6.0

Copyright 2008-2010, The Perl Foundation

[17​:47] <masak> bbkr​: there's no underlying semantics for it, though.
[17​:48] <masak> bbkr​: that is to say, 'my @​a[5]' works like 'my @​a'
right now.

[17​:52] <bbkr> masak​: there is ticket about fixed-size arrays #​67600 -
maybe it should be renamed to "[TODO] implement ..." instead of current
"Cannot declare", as Rakudo already parses this syntax
[17​:53] <masak> bbkr​: if it's "Cannot declare...", it should be closed.

@p6rt
Copy link
Author

p6rt commented Aug 3, 2010

The RT System itself - Status changed from 'new' to 'open'

@p6rt
Copy link
Author

p6rt commented Aug 3, 2010

@bbkr - Status changed from 'open' to 'resolved'

@p6rt p6rt closed this as completed Aug 3, 2010
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant