John Keiser wrote:
> Which one of you is working on that? I have heard you each talk about it.
> I could give it a go if it's still in the formative stages and you two have
> other stuff to do.
I'll check in the Javadoc API I've already coded up. Basically, here are my
thoughts. We need several components to be written:
-- The com.sun.javadoc package, which I have already done
-- A JDK 1.2 compatible doclet
-- A JDK 1.1 compatible doclet
-- A Texinfo generation doclet
-- A parser engine
-- A driver program
-- Documentation
As you can see, a lot of this is parallelalizable. Per usual I was thinking
of something more ambitious. To the best of my knowledge there is no
standard parsing API. I was thinking that there should be a "parselet" API
for applications that need to parse Java source files (JavaDeps, JavaDoc,
etc). This should make it fairly easy to write programs that operate on
Java source without having muck around with your own parser engine. But
that concept was as far as I got.
On the driver side, I have been messing with an abstract Tool class that
handles certain basic functions. I should clean that up and check something
in on it too. My getopt program should be used for command line options.
Be sure to put all user messages (including the help and usage text) in a
ResourceBundle for internationalization. Follow the GNU standards for
program behavior.
If I think of anything else I'll send it off.
--
Aaron M. Renn ([EMAIL PROTECTED]) http://www.urbanophile.com/arenn/
