I forgot to mention... when I said code self-documentation, I meant that there are places where I have a component or page that takes two models. Which is which? I document it by the parameter name (i.e. MyComponent(IModel fooModel, IModel barModel), but it is much better (and the compiler checks it for me) having MyComponent(IModel<Foo> fooModel, IModel<Bar> barModel).
-- Jeremy Thomerson http://www.wickettraining.com On Thu, May 22, 2008 at 8:32 AM, Jeremy Thomerson <[EMAIL PROTECTED]> wrote: > I haven't said anything up to this point, but we really don't seem to be > getting anywhere with what is turning into a religious war. I, for one, > have already started using 1.4, and love the generics, despite the extra > verbosity. It gives me extra type safety and code self-documentation. I > would be very against having the framework do a cast as has been suggested > on here, because that is a hack, and not useful for anything - I lose the > value of generics because the compiler is no longer checking my type safety > throughout the application. If I came to a framework without previous > experience with it, and discovered that ugly hack, I would be worried about > the quality of all of the code. > > I think that we should: > - continue with 1.4-M2 > - create a wiki page where we can get one master list of things we like > and don't like > - see what we can do to address those > > We're really not getting anywhere with this conversation until we have a > finite list, and some options for each con on the list. Then we can either > choose the best options or say "forget it". > > -- > Jeremy Thomerson > http://www.wickettraining.com > > On Thu, May 22, 2008 at 6:23 AM, Jan Kriesten <[EMAIL PROTECTED]> > wrote: > >> >> hi sebastiaan, >> >> I'm very much against using generics to do something other from what >>> generics where meant to do (i.e., type safety). >>> >> >> i'm all in when you're talking about type safety. having compile-time >> checks on the types is a time-saver during development. >> >> with wicket generics it's just that the time-saver get's in it's own way, >> i.e. bringing in so much boilerplate, that coding is getting harder to do >> right (besides from source readability). >> >> >> regards, --- jan. >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> > > > >
