Hey, from the developers of Fan who implemented Not-Null-Types in Fan (I think modeled after Nice) some said after converting their complete API to default not-null:
"So only 16% of all the slots use nullable types. Only 8% of all methods return a nullable type. So empirical evidence does indeed suggest that non-nullable is the common case." http://www.fandev.org/sidewalk/topic/372 So it's much more sensible to have @Optional than @NotNull Peace Stephan On Mon, Nov 3, 2008 at 7:18 PM, Rickard Öberg <[EMAIL PROTECTED]> wrote: > Hey, > > Just checking, should I go ahead and implement @Optional? I.e. assume > that all method parameters are non-null by default (and throw NPE if > they are null), and then allow setting @Optional as an annotation if the > value can be null. This would remove the @NotNull constraint in the > process, which seems like a good thing (as it is used almost everywhere > now). > > /Rickard > > _______________________________________________ > qi4j-dev mailing list > [email protected] > http://lists.ops4j.org/mailman/listinfo/qi4j-dev > -- Stephan Schmidt :: [EMAIL PROTECTED] Reposita Open Source - Monitor your software development http://www.reposita.org Blog at http://stephan.reposita.org - No signal. No noise. _______________________________________________ qi4j-dev mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/qi4j-dev
