Giannakopoulos, It's a debate that goes on. Josh Bloch in his Effective Java book says NPE is perfectly acceptable for bad arguments. So it really depends on your perspective what an NPE represents. I prefer Josh's opinion but only because every single argument probably creates lots of branch-checking that kills cpu pipelining.
Paul On Tue, Mar 1, 2011 at 2:01 PM, Michael Giannakopoulos <miccagi...@gmail.com > wrote: > Hello guys, > > As far as this issue is concerned (for what i have understood) i believe > that one way to separate NULL(s) that occur from the A.P.I. from NULL(s) > coming from wrong usage of A.P.I. by a user is the assert technique... I > didn't know a lot about it but from what i have read it should be > implemented only in the private methods of the A.P.I. Check this link out: > " > http://download.oracle.com/javase/1.4.2/docs/guide/lang/assert.html";. > Another choice is to create a new class that would check all the arguments > of every function we are interested in (for example: public > checkArguments(Object... args)) [If i have understood correctly the purpose > of this issue...]. Any suggestions would be more than welcomed! > > Best regards, > Giannakopoulos Michael >
