[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [eclipse.org-architecture-council] Encourage projects to use JDT null analysis & null annotations for Neon
|
> Am 28.09.2015 um 18:15 schrieb Daniel Megert <daniel_megert@xxxxxxxxxx>:
>
> > I had feared that :-) How about simply running JDT null analysis on every source method and let the compiler infer the possible values for parameters and method return values?
> In our Eclipse world the API i.e. Javadoc defines the contract, hence inferring it from the source code would be wrong.
If this is done consistently and completely, one could infer that from Javadoc comments as well.
> > So, how could we start? Is Platform (or parts of it like JFace Databinding) leading the way, blogging about it and encouraging people?
> I don't see why it has to be Platform to blog about this or lead the way. Other projects are welcome to do that work ;-)
It’s a difference whether a tiny leaf project is doing so or „the platform“ ;-)
> > Do we have or get resources to run the JDT null analysis on source code and see how far we get with this?
> Sorry, I don't fully understand that question or at least its scope.
Reformulating: Since the JDT committers know their tools much better than anyone else on the planet: how much effort would it be to provide a basic tool that runs the null simulation / analysis on an Eclipse workspace and outputs a text file with its findings?
And: Can an JDT committer provide that code skeleton?
From there, others (like me) can take over and build the necessary tooling around this.
Marcel
