Coin Considerations (original) (raw)

Dalibor Topic Dalibor.Topic at Sun.COM
Sat Mar 14 10:47:08 PDT 2009


Reinier Zwitserloot wrote:

I like that idea. So, you mean the entire source code, all of it, as one annotation (vs. a path)?

Yeah. Supplying the sources behind the line information referenced in other portions of debug info, basically. Dumping the entire source code for a file rather then subsets has the advantage that correct licensing, javadoc and attribution information could trivially travel along with the generated binary class file.

I picked StoredSource rather then OpenSource, as the latter would have a pretty specific meaning, whereas I guess the proprietary software devs could make efficient use of such a feature, too.

I'd see is as an addition to the predefined annotations, so it would require adding its spec to §9.6.1, at least.

It's more of a small productivity booster for those 'where is the source for this apparently semi-random snapshot JAR on my classpath that I'm getting this weird exception from' moments, then a real change of the language.

On the con side, it may require some fiddling with JVMTI & friends to expose the stored source code in a standard way to IDEs and debugging tools. So I'm not really sure if it fits into the Coin domain, but since you asked I figured I'd come out with the half-baked idea.

If the idea sounds useful, I'll play with it a bit further - but feel free to run with it yourself.

cheers, dalibor topic

--


Dalibor Topic Tel: (+49 40) 23 646 738 Java F/OSS Ambassador AIM: robiladonaim Sun Microsystems GmbH Mobile: (+49 177) 2664 192 Nagelsweg 55 http://openjdk.java.net D-20097 Hamburg mailto:Dalibor.Topic at sun.com Sitz der Gesellschaft: Sonnenallee 1, D-85551 Kirchheim-Heimstetten Amtsgericht München: HRB 161028 Geschäftsführer: Thomas Schröder, Wolfgang Engels, Dr. Roland Bömer Vorsitzender des Aufsichtsrates: Martin Häring



More information about the coin-dev mailing list