> > Yep, you could. Though some constructors in other classes (in or > > outside Wicket) might expect not-null arguments passed in in > > constructors. It just depends on who implemented it. There is no > > golden pattern that everyone follows; if there was, it should probably > > be enforced in the language. > > Thanks. I agree there is no golden pattern, but to have in jdk something like > @Nullable and @NotNull would be nice :)
Or we need a better language :-) See for instance http://gbracha.blogspot.com/2007/06/constructors-considered-harmful.html (great post, don't forget to read the comments) Eelco --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
