[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [equinox-dev] Coding standards: using import abc.* - or not?
- From: Benjamin Reed <breed@xxxxxxxxxxxxxxx>
- Date: Fri, 11 Nov 2005 09:39:41 -0800
- Delivered-to: firstname.lastname@example.org
- Organization: IBM Almaden Research Center
- User-agent: KMail/1.8.3
On Friday 11 November 2005 08:20 am, Oleg Besedin wrote:
> Hi Everybody,
> The Equinox coding standard says that imports should be coalesced ("import
> abc.*") if 3 or more classes are imported from the same package
> However, this brings a rather real problem that we just had a chance to
> In this case a plugin was using:
> import abc.*;
> import myPackage.Assert;
> Which was fine - until the Assert class was added into the other plugin's
> package abc.
> Clearly, "import abc.*" introduces ambiguity. On the other hand, Eclipse's
> "Organize Imports" command lets developers easily manage individual
> imports. And, last but not least, in my opinion, seeing all individual
> imports helps understand where imported classes actually come from and
> adds to that nice warm feeling of being in control.
> With all this in mind, should we change the Equinox coding standard to
> don't coalesce the imports?
> Oleg Besedin