test all parrot command line flags #346

Open
coke opened this Issue Oct 28, 2009 · 4 comments

Comments

Projects
None yet
4 participants
@coke
Contributor

coke commented Oct 28, 2009

Update t/run/options.t to test all command line flags, as well as some invalid ones.

See original ticket at http://rt.perl.org/rt3/Ticket/Display.html?id=42339

Originally http://trac.parrot.org/parrot/ticket/1150

@jkeenan

This comment has been minimized.

Show comment Hide comment
@jkeenan

jkeenan Feb 25, 2011

Contributor

darbelo,

Have you been able to make any progress on this ticket?

Thank you very much.

kid51

Contributor

jkeenan commented Feb 25, 2011

darbelo,

Have you been able to make any progress on this ticket?

Thank you very much.

kid51

@Benabik

This comment has been minimized.

Show comment Hide comment
@Benabik

Benabik Jan 26, 2012

Member

Thorough testing of command line options would have caught the issue in #185 sooner.

Member

Benabik commented Jan 26, 2012

Thorough testing of command line options would have caught the issue in #185 sooner.

@Benabik

This comment has been minimized.

Show comment Hide comment
@Benabik

Benabik Jan 26, 2012

Member
Member

Benabik commented Jan 26, 2012

@ghost ghost assigned bschmalhofer and Benabik Feb 7, 2012

@Benabik

This comment has been minimized.

Show comment Hide comment
@Benabik

Benabik Feb 7, 2012

Member

I've hit three issues:

Issue 1: I'm not sure how to actually test the library path (-I, -L, -X) and GC options.

Issue 2: The following IMCC options appear to be wholly disconnected. They are listed in --help, docs/running.pod, and even seem to be parsed. However, they don't actually do anything.

  • -d / --imcc-debug
  • -v / --verbose
  • -O / --optimize
  • -y / --yydebug

It's been suggested that the best thing to do with them is to just remove them. Some could be hooked up to actual code, as the machinery in IMCC for debugging and yydebug still exist.

Issue 3: The -p / --profile option is listed in docs/running.pod, but doesn't appear to actually exist. Is this expected to work in any way?

Member

Benabik commented Feb 7, 2012

I've hit three issues:

Issue 1: I'm not sure how to actually test the library path (-I, -L, -X) and GC options.

Issue 2: The following IMCC options appear to be wholly disconnected. They are listed in --help, docs/running.pod, and even seem to be parsed. However, they don't actually do anything.

  • -d / --imcc-debug
  • -v / --verbose
  • -O / --optimize
  • -y / --yydebug

It's been suggested that the best thing to do with them is to just remove them. Some could be hooked up to actual code, as the machinery in IMCC for debugging and yydebug still exist.

Issue 3: The -p / --profile option is listed in docs/running.pod, but doesn't appear to actually exist. Is this expected to work in any way?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment