| javap and -noqualifier option [message #29819] |
Wed, 02 March 2005 16:13  |
Eclipse User |
|
|
|
Originally posted by: testaccount9426.yahoo.com
When generating a javadoc for a project
(File=>Export=>Javadoc=>Next=>Finish), is there any way to cause Eclipse
to invoke javap.exe with the -noqualifier option, so that the generated
html does not include package references. (For instance, "public void
fooBar(String s)" is rendered in the javadoc as "fooBar(String s)" and not
as "fooBar(java.lang.String s)".)
|
|
|
| Re: javap and -noqualifier option [message #29845 is a reply to message #29819] |
Thu, 03 March 2005 11:24  |
| Eclipse User |
|
|
|
Originally posted by: first_dot_last.somanetworks.com
Stephen S. Ashley wrote:
> When generating a javadoc for a project
> (File=>Export=>Javadoc=>Next=>Finish), is there any way to cause Eclipse
> to invoke javap.exe with the -noqualifier option, so that the generated
> html does not include package references. (For instance, "public void
> fooBar(String s)" is rendered in the javadoc as "fooBar(String s)" and
> not as "fooBar(java.lang.String s)".)
>
Stephen,
You are making the incorrect assumption that the Java name-space is
hierarchical. It is *not*, it is flat. What this means is the two classes:
java.lang.String and
com.mystuff.String
are NOT the same, if you remove the "package" portion of the name-space,
you get ambiguous names for the "String" class.
Now granted, the String example is simple, but there is no "package"
part of the name-space, the whole string is all part of the Java class
name. Packages are just a way to organize the classes name-space for
mere mortals like us to read. The "import" statement is like the
#include <> statements in C/C++ and IMHO the "import package.*;" (wild
card) is a hack in the language. It promotes lazy coding.
Hope this clears things up for you,
ronw
|
|
|
Powered by
FUDForum. Page generated in 0.08490 seconds
Home