Would I be correct in assuming that the majority of java.sql would be
trivial to implement by reading the javadocs (everything except
DriverManager)? I can take a whack at the low hanging fruit this
weekend.
Jeremy
On 10-Feb-06, at 12:05 PM, zoe slattery wrote:
Upayavira wrote:
zoe
On 10-Feb-06, at 1:14 PM, Tor-Einar Jarnbjo wrote:
Jeremy Huiskamp schrieb:
Would I be correct in assuming that the majority of java.sql would
be trivial to implement by reading the javadocs (everything
except DriverManager)? I can take a whack at the low hanging
fruit this weekend
What would be the suggested route for coming up with a javadoc tool?
Is there something out there now that could be imported and shaped
up? At the other extreme, I'm envisioning busting out jflex/cup and
doing a from-scratch implementation. I'm thinking there would be a
lot of
, at 1:41 PM, Geir Magnusson Jr wrote:
Jeremy Huiskamp wrote:
What would be the suggested route for coming up with a javadoc tool?
Open up an editor, and start typing! :)
Is
there something out there now that could be imported and shaped
up? At the other extreme, I'm envisioning busting out
://eclipsecon.org/2005/presentations/EclipseCON2005_Tutorial29.pdf
...
specifically the javadoc node
Regards,
Tim
Jeremy Huiskamp wrote:
First the disclaimer: I have zero experience with writing such
tools and
precious little with compilers. I'm just spewing what I think but if
there are accepted ways
I was wondering about this myself. I went and slogged through the
epl and had trouble gathering exactly what the license restrictions
were. From what I could tell, most of it was just disclaimer. What
is the official apache stance on epl code?
Jeremy
On 9-Feb-06, at 11:48 PM, Anthony
