Stuart -
This sounds great to me, since I am all for automatically doing =
anything. I
mean, that's what we programmers are for! However, before you get too
carried away, and since you know how to script in Perl, why don't you =
take a
look at this: http://jsdoc.sourceforge.net
It may not do exactly what we want, and (having reviewed it a bit) I =
don't
think it follows the JavaDoc standard as much as we have. But, this =
could
be just the thing we needed. Since it is an open source project, we =
could
take the scripts and modify them freely to fit our needs, as long as we
relay the good news to the development team. What do you think, =
partner?
Cheers,
Randy
-----Original Message-----
From: jsp...@li...
[mailto:jsp...@li...] On Behalf Of Stuart =
Wigley
Sent: Thursday, September 11, 2003 8:37 AM
To: jsp...@li...
Subject: [Jspro-devel] New @summary commenting tag
Hi Randy,
I've been playing around with writing a Perl script to
generate the README file - i guess you could consider
it the first step in a javascript comments parser, and
also I'm too lazy to keep updating the README file
manually :-)
Anyway, during this process I thought it would be
useful to invent a @summary comment for holding a very
brief summary of the method - ie one or two words.
Does this sound ok to you? I'll check the perl script
in soon - at the moment its messy as hell and isn't
complete.
Cheers
Stuart
________________________________________________________________________
Want to chat instantly with your online friends? Get the FREE Yahoo!
Messenger http://mail.messenger.yahoo.co.uk
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Jspro-devel mailing list
Jsp...@li...
https://lists.sourceforge.net/lists/listinfo/jspro-devel
|
