FYI, the Project Lambda Streams code and JSR-310 in JDK 1.8 are both written with static imports in mind. Moreover, with support for static methods in interfaces being added, this is likely to increase as a pattern. Those facts may or may not affect decisions in commons.
Stephen On 4 February 2013 21:32, Benedikt Ritter <brit...@apache.org> wrote: > Hi, > > we had a little discussion in BeanUtils2, regarding static imports (see > below). To increase visibility and get some more feedback, I'm forwarding > this to [ALL] > > We haven't decided yet how to handle static imports. To form some rules, > we'd like to hear what others think about static imports and what rules of > thumb you use in your projects. > > I'm exited to hear your opinions :) > Regards, > Benedikt > > > 2013/2/4 Jörg Schaible <joerg.schai...@scalaris.com> > >> Hi, >> >> Benedikt Ritter wrote: >> >> > Hi Simo, >> > >> > thanks for sharing your thoughts! I personally try to avoid static >> > imports. Especially when you come to a legacy code base IMHO it makes the >> > code harder to understand. You always have to look, where a method comes >> > from. >> >> Actually I avoid static imports for the same reason. >> >> > Also you may have the problem, that you accidentally override >> > imported static methods, when defining a new static method with the same >> > name. BU2 is a very small code base, so it would be okay for me to revert >> > the change. >> > >> > Nevertheless I'd be interested to hear what others thing about this >> topic. >> >> my 2¢ >> >> - Jörg >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org >> For additional commands, e-mail: dev-h...@commons.apache.org >> >> --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
