ooh. actually this is incorrect too.
for 1, it's the object directly for 2, there is only ONE node (because of left/right pointers!) for N, there are N - 1 node objects and the cases of 1 or 2 validators is really the majority. Phil Kulak wrote:
Well, right now you're doing exactly what LinkedList does. You're wrapping every object in a node and including two object references. Where's the space savings? You could get rid of half the objects by using an array and essentially reimplementing ArrayList. The downside here is that if I add a string validator to a RequiredTextField, I have no gaurantees that the value I get will be non-null. I do like what you did with the booleans though. That's tight. :) ------------------------------------------------------- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf _______________________________________________ Wicket-develop mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-develop
------------------------------------------------------- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf _______________________________________________ Wicket-develop mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-develop
