I't really does not matter much but I'm with Eelco and Johan on this. I prefer not to allow null values in the constructor. At least not if there is a constructor with fewer parameters that can be used instead. So I prefer to chain towards the simpler constructor if possible.
On 8/24/07, Martin Funk <[EMAIL PROTECTED]> wrote: > Eelco Hillenius schrieb: > >> private component init(String, IModel) which can assume null arguments > >> > >> do the null checks in the constructor and forward to that method > >> > > > > That's an option in general, though the disadvantage of that is that > > you can't use final fields. > > > > Anyway, for this case, if anyone cares, we can fix it in either way. > > > I care. > Is that enough anyones? > > mf > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
