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

harness5 misreports its options #6036

Closed
p6rt opened this issue Jan 28, 2017 · 4 comments
Closed

harness5 misreports its options #6036

p6rt opened this issue Jan 28, 2017 · 4 comments

Comments

@p6rt
Copy link

p6rt commented Jan 28, 2017

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

Searchable as RT130659$

@p6rt
Copy link
Author

p6rt commented Jan 28, 2017

From @toolforger

harness5 has --moar, which is used in makefiles, and I think the code
also defines a --jvm.
Neither --moar nor --jvm are reported with --help.

The POD section in harness5 carries most options in its SYNOPIS, but
neither --moar nor --jvm, so I suppose that the --help output is
generated from an outdated SYNOPSIS section.

I am too busy with other stuff so I couldn't verify the "I suppose"
part, and I have not looked into harness6 which may or may not have
similar issues.

@p6rt
Copy link
Author

p6rt commented Jan 31, 2017

From @zoffixznet

On Sat, 28 Jan 2017 02​:06​:01 -0800, toolforger@​durchholz.org wrote​:

harness5 has --moar, which is used in makefiles, and I think the code
also defines a --jvm.
Neither --moar nor --jvm are reported with --help.

The POD section in harness5 carries most options in its SYNOPIS, but
neither --moar nor --jvm, so I suppose that the --help output is
generated from an outdated SYNOPSIS section.

I am too busy with other stuff so I couldn't verify the "I suppose"
part, and I have not looked into harness6 which may or may not have
similar issues.

Thank you for the report. Both t/harnesses are now fixed.

Fix​: rakudo/rakudo@43666039ae
Test​: none needed

@p6rt
Copy link
Author

p6rt commented Jan 31, 2017

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

@p6rt
Copy link
Author

p6rt commented Jan 31, 2017

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

@p6rt p6rt closed this as completed Jan 31, 2017
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