[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [equinox-dev] Coding standards: using import abc.* - or not?
- From: Peter Kriens <Peter.Kriens@xxxxxxxx>
- Date: Mon, 14 Nov 2005 13:41:36 +0100
- Delivered-to: firstname.lastname@example.org
- Organization: aQute
I like the import abc.* very much because it is easier to see what
packages are used, less redundant information is easier to grasp.
Coupling takes place on package level, not class level. The root of
most software evil is redundancy.
I do not understand the problems:
- Identical names are rare and confusing anyway.
- F3 brings you to the definition regardless of the import
NH> On Saturday 12 November 2005 00:20, Oleg Besedin wrote:
>> With all this in mind, should we change the Equinox coding standard to
>> don't coalesce the imports?
NH> Personally I don't like the abc.* imports, largely due to my habit of not
NH> using IDEs, where going looking for referenced classes is a pain with such
NH> So, when the day come of me diving into the Equinox codebase, I would be happy
NH> if it didn't have such, but I think it is becoming a lesser and lesser
NH> concern by the constant increase of IDE usage.
NH> equinox-dev mailing list
Peter Kriens Tel +33870447986
9C, Avenue St. Drézéry AOL,Yahoo: pkriens
34160 Beaulieu, France ICQ 255570717
Skype pkriens Fax +1 8153772599