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

perl6 option handling - insufficiently paranoid #66

Closed
p6rt opened this issue Mar 29, 2008 · 9 comments
Closed

perl6 option handling - insufficiently paranoid #66

p6rt opened this issue Mar 29, 2008 · 9 comments

Comments

@p6rt
Copy link

p6rt commented Mar 29, 2008

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

Searchable as RT52242$

@p6rt
Copy link
Author

p6rt commented Mar 29, 2008

From ajr@ippimail.com

Perl 6 does not defend itself against invalid options. Using an invalid
option results in an ungraceful death rather than a valid error message.

E.g.
$ ./perl6 -x "say 'Hi';"
Error​: file cannot be read​: -x
current instr.​: 'parrot;PCT​::HLLCompiler;panic' pc 158
(src/PCT/HLLCompiler.pir​:103)

--
 
Email and shopping with the feelgood factor!
55% of income to good causes. http://www.ippimail.com

@p6rt
Copy link
Author

p6rt commented Mar 30, 2008

From @pmichaud

On Sat, Mar 29, 2008 at 12​:53​:29PM -0700, Alan Rocker wrote​:

Perl 6 does not defend itself against invalid options. Using an invalid
option results in an ungraceful death rather than a valid error message.

E.g.
$ ./perl6 -x "say 'Hi';"
Error​: file cannot be read​: -x
current instr.​: 'parrot;PCT​::HLLCompiler;panic' pc 158
(src/PCT/HLLCompiler.pir​:103)

Earlier this year there was some discussion of defining a set
of standard command-line options that would be common to all
Perl 6 implementations, and so we've been holding off on
argument processing until that's resolved a bit more. I haven't
heard much more about it since January -- perhaps we should poke
perl6-language for ideas...?

Thanks!

Pm

P.S.​: Send bug reports for Rakudo/perl6 to <rakudobug@​perl.org> --
it helps us keep the tickets straight and discussions in the
correct mailing list.

@p6rt
Copy link
Author

p6rt commented Mar 30, 2008

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

@p6rt
Copy link
Author

p6rt commented Mar 31, 2008

From ajr@ippimail.com

and so we've been holding off on argument processing until that's
resolved a > bit more.

Should it matter what's in the "allowed" class? From the beginning, there
ought to be a default "if I don't know what this is, spit it back" action.
What happens before that point is irrelevant.

P.S.​: Send bug reports for Rakudo/perl6 to <rakudobug@​perl.org> --
Will do.

--
 
Email and shopping with the feelgood factor!
55% of income to good causes. http://www.ippimail.com

@p6rt
Copy link
Author

p6rt commented Sep 26, 2008

From @masak

Rakudo r31409 assumes that all flags that it hasn't heard about are
program files.

$ ./perl6 --help
./perl6
Usage​: perl6 [switches] [--] [programfile] [arguments]
[...]
$ ./perl6 --kelp # a kind of seaweed
Error​: file cannot be read​: --kelp
[...]
$ touch -- --kelp
$ ./perl6 --kelp # quietly succeeds

@p6rt
Copy link
Author

p6rt commented Nov 26, 2008

@pmichaud - Status changed from 'open' to 'stalled'

@p6rt
Copy link
Author

p6rt commented Nov 26, 2008

From @pmichaud

On Fri, Sep 26, 2008 at 02​:55​:36AM -0700, Carl Mäsak wrote​:

Rakudo r31409 assumes that all flags that it hasn't heard about are
program files.

$ ./perl6 --help
./perl6
Usage​: perl6 [switches] [--] [programfile] [arguments]
[...]
$ ./perl6 --kelp # a kind of seaweed
Error​: file cannot be read​: --kelp
[...]
$ touch -- --kelp
$ ./perl6 --kelp # quietly succeeds

This is likely to be fixed as part of S19 development, so I'm
marking this ticket as stalled until then.

Pm

@p6rt
Copy link
Author

p6rt commented Sep 30, 2011

From @moritz

Now dies with "no such option -x"

@p6rt
Copy link
Author

p6rt commented Sep 30, 2011

@moritz - Status changed from 'stalled' to 'resolved'

@p6rt p6rt closed this as completed Sep 30, 2011
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