Bug 164713 - jcf-dump documentation is incomplete (and confusing)
Summary: jcf-dump documentation is incomplete (and confusing)
Status: CLOSED UPSTREAM
Alias: None
Product: Fedora
Classification: Fedora
Component: gcc4
Version: 4
Hardware: All
OS: Linux
medium
low
Target Milestone: ---
Assignee: Jakub Jelinek
QA Contact:
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2005-07-30 21:25 UTC by Paul Bolle
Modified: 2007-11-30 22:11 UTC (History)
0 users

(edit)
Clone Of:
(edit)
Last Closed: 2005-08-05 22:19:22 UTC


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
GNU Compiler Collection 23258 None None None Never

Description Paul Bolle 2005-07-30 21:25:56 UTC
Description of problem:
The documentation of jcf-dump is incomplete (and confusing)

Version-Release number of selected component (if applicable):
gcc-java-4.0.1-4.fc4


How reproducible:
Always

Steps to Reproduce:
1. n/a
2.
3.
  
Actual results:
n/a

Expected results:
n/a

Additional info:
0) man jcf-dump and info jcf-dump are (basically) identical. Neither mention:
--bootclasspath
--extdirs
--print-main

1) jcf-dump --help doesn't mention:
--CLASSPATH
--print-main
--print-constants

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

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

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

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

6) Should I file a bug upstream? If so, what is the actual gcc component involved?

Comment 1 Jakub Jelinek 2005-08-05 22:19:22 UTC
Yes, this should be definitely filed upstream, not here.
http://gcc.gnu.org/bugzilla/, component libgcj.
When it is fixed upstream, it will eventually make it into Fedora Core packages.

Comment 2 Paul Bolle 2005-08-06 04:51:35 UTC
OK, I've done that. Upstream is http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23258


Note You need to log in before you can comment on or make changes to this bug.