Re: proposal for performance/usability optimisations in commons.lang.Validate

2009-06-07 Thread Mark Struberg
...@yahoo.de schrieb am Do, 7.5.2009: Von: Mark Struberg strub...@yahoo.de Betreff: Re: proposal for performance/usability optimisations in commons.lang.Validate An: Commons Developers List dev@commons.apache.org Datum: Donnerstag, 7. Mai 2009, 11:23 Thanks a lot Henri! I talked with Shawn

Re: proposal for performance/usability optimisations in commons.lang.Validate

2009-05-07 Thread Henri Yandell
trunk/ is now JDK 5 focused. It'll be Lang 3.0, but is very unlikely to keep the same package naming. My biggest concern with ellipsis code is that null moves from being null to being null inside an Object[]. So we could see some unnecessary API changing if we're not careful. Otherwise - the

Re: proposal for performance/usability optimisations in commons.lang.Validate

2009-05-07 Thread Mark Struberg
Thanks a lot Henri! I talked with Shawn Pearce about possible performance issues and we now ended up with 3 function groups: notNull(Object) notNull(Object, String) notNull(Object, String, Object...); So the JVM doesn't need to create an Object[] if we only like to provide a single String

proposal for performance/usability optimisations in commons.lang.Validate

2009-05-02 Thread Mark Struberg
Hi! I'm a long time user (and big fan) of commons.lang.Validate because it's a very neat pattern for getting stable software modules. I'm PMC member on Apache OpenWebBeans and currently also writing the maven-scm-provider-jgit (JGIT is a native Java implementation of GIT). Since jgit-core