[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [equinox-dev] Coding standards: using import abc.* - or not?
- From: Niclas Hedhman <niclas@xxxxxxxxxxx>
- Date: Sun, 20 Nov 2005 10:22:36 +0800
- Delivered-to: firstname.lastname@example.org
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:from:organization:to:subject:date:user-agent:references:in-reply-to:mime-version:content-disposition:message-id:content-type:content-transfer-encoding:sender; b=AGLM33B7Sf6EMj8hE42B2uDJHskegtLbxVFS/I2CbrSeNH8dBo/qQUqjSQHh+RrspovkU02XTcF1gU6poORXPjfuQpp/nQKuo84oN3vooQMyMmimUk+3rf60bDfJisY2N8Eg9pIqmopT6Y54G6lLApm8KQwi3AGIjbQiiZhgz4o=
- Organization: Independent
- User-agent: KMail/1.8
On Monday 14 November 2005 20:41, you wrote:
> I like the import abc.* very much because it is easier to see what
> packages are used, less redundant information is easier to grasp.
Perhaps such support could be added in Eclipse instead ?? I.e. Let the Code
Folding fold the import statements in "two steps", one for packages and one
for the entire imports.
IMHO, this should satisfy everyone involved.
> Coupling takes place on package level, not class level. The root of
> most software evil is redundancy.
I totally agree!