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

Internal error when passing whitespace through a named argument in Rakudo #4714

Closed
p6rt opened this issue Nov 1, 2015 · 4 comments
Closed
Labels

Comments

@p6rt
Copy link

p6rt commented Nov 1, 2015

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

Searchable as RT126532$

@p6rt
Copy link
Author

p6rt commented Nov 1, 2015

From @masak

Basically, any argument containing only whitespace seems to trigger
this error. It seems that the presence of the MAIN sub is part of the
error; remove it and it accepts all of the inputs causing an error
below.

$ cat x.pl
sub MAIN {}

$ perl6 x.pl -y=' '
Cannot invoke this object
  in block <unit> at x.pl​:1

$ perl6 x.pl -y=''
Cannot invoke this object
  in block <unit> at x.pl​:1

$ perl6 x.pl -y=`perl -E'say "\n"'`
Cannot invoke this object
  in block <unit> at x.pl​:1

$ perl6 x.pl -y=`perl -E'say "\t"'`
Cannot invoke this object
  in block <unit> at x.pl​:1

$ perl6 x.pl -y=`perl -E'say "\t "'`
Cannot invoke this object
  in block <unit> at x.pl​:1

$ perl6 --version
This is perl6 version 2015.10-89-g36c4c6a built on MoarVM version
2015.10-14-g5ff3001

@p6rt
Copy link
Author

p6rt commented May 9, 2018

From @skids

The examples would fail usage constraints with the parameterless MAIN.
I could not get them to fail with any internal messages on current rakudo,
either with the parameterless MAIN or with a MAIN that had a :$y.

Haven't looked as to when this got fixed.

Tests added for both cases (though I had to add a sub USAGE when testing
the parameterless case) in Raku/roast@bdf67b698b,
so closing as resolved.

@p6rt
Copy link
Author

p6rt commented May 9, 2018

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

@p6rt
Copy link
Author

p6rt commented May 9, 2018

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

@p6rt p6rt closed this as completed May 9, 2018
@p6rt p6rt added the Bug label Jan 5, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant