Bug 23258 - jcf-dump documentation is incomplete (and confusing)
Summary: jcf-dump documentation is incomplete (and confusing)
Alias: None
Product: gcc
Classification: Unclassified
Component: libgcj (show other bugs)
Version: 4.0.1
: P3 enhancement
Target Milestone: ---
Assignee: Not yet assigned to anyone
Keywords: documentation
Depends on:
Reported: 2005-08-06 04:46 UTC by Paul Bolle
Modified: 2016-09-30 22:49 UTC (History)
2 users (show)

See Also:
Known to work:
Known to fail:
Last reconfirmed: 2005-08-06 06:10:43


Note You need to log in before you can comment on or make changes to this bug.
Description Paul Bolle 2005-08-06 04:46:56 UTC
0) Previously filed downstream here:

1) man jcf-dump and info jcf-dump are (basically) identical. Neither mention:

2) jcf-dump --help doesn't mention:

3) Neither info/man nor --help mention that you can use jcf-dump on (all classes
in) a jar archive.

4) Nowhere in the documentation is it stated clearly that you can jcf-dump
classfiles (not just classes).

5) The description of -o in man and info is slightly puzzling: "Th[is] options
[is] the same as the corresponding gcj option(...)."

6) The descriprition of --extdirs in --help is also intruiging: "Set extensions
directory path". That doesn't seem sufficient to me.

7) I'm happy to submit patches if needed (though you're probably better of with
patches from (one of) the maintainers).
Comment 1 Andrew Pinski 2005-08-06 06:10:43 UTC
Comment 2 Andrew Pinski 2016-09-30 22:49:51 UTC
Closing as won't fix as libgcj (and the java front-end) has been removed from the trunk.