Mailing-List: contact dev-help@commons.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Commons Developers List" <dev@commons.apache.org>
Received-SPF: pass (athena.apache.org: domain of jodastephen@gmail.com
 designates 209.85.128.177 as permitted sender)
MIME-Version: 1.0
Sender: jodastephen@gmail.com
In-Reply-To: 
 <CAB917R+=A9sL=j4DxxdsJ_cL70ZT3zaz1UDubjPg7AzHFxH9KQ@mail.gmail.com>
References: 
 <CAB917R+=A9sL=j4DxxdsJ_cL70ZT3zaz1UDubjPg7AzHFxH9KQ@mail.gmail.com>
From: Stephen Colebourne <scolebourne@joda.org>
Date: Tue, 5 Feb 2013 11:13:47 +0000
Message-ID: 
 <CACzrW9Atoe1VVgPAHq1jgDGmYhtRSse4=Dt-4GrHCfBQhX62Ww@mail.gmail.com>
Subject: Re: [ALL] How to handle static imports [was: Re: svn commit: r1441784
 -
 /commons/sandbox/beanutils2/trunk/src/main/java/org/apache/commons/beanutils2/PropertyDescriptorsRegistry.java]
To: Commons Developers List <dev@commons.apache.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

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 <britter@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 o=
f
> thumb you use in your projects.
>
> I'm exited to hear your opinions :)
> Regards,
> Benedikt
>
>
> 2013/2/4 J=F6rg Schaible <Joerg.Schaible@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 com=
es
>> > 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 sa=
me
>> > name. BU2 is a very small code base, so it would be okay for me to rev=
ert
>> > the change.
>> >
>> > Nevertheless I'd be interested to hear what others thing about this
>> topic.
>>
>> my 2=A2
>>
>> - J=F6rg
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>> For additional commands, e-mail: dev-help@commons.apache.org
>>
>>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org