Hi Dave,
In Eclipse, when you auto-import classes, it propose you to pick the best
one in a popup list, so it's very easy to resolve those conflicts.
Otherwise, it's just too hard to take into account all potential name
conflicts, especially when names (inspired from REST and HTTP) are core
I use netbeans too and it behaves just like eclipse it proposes
potential imports and you import one.
Till now I haven't had this problem of direct conflict with java(x).*
packages. Dave are you referring to a sun.* package? Could you please
give a specific example?
Checkstyle can check for
Objet : Re: name conflicts
On 17/11/06, Jerome Louvel [EMAIL PROTECTED] wrote:
In Eclipse, when you auto-import classes, it propose you to
pick the best
one in a popup list, so it's very easy to resolve those conflicts.
Ditto with netbeans. That assumes that we should take the supposed
On 17/11/06, Chris Grindstaff [EMAIL PROTECTED] wrote:
I agree, this is a non-issue.
Let's not bastardize the good names we have. Especially the ones that
directly map to Roy's dissertation. I think the direct mapping is very
helpful.
OK by me. I've worked past it mostly.
I'm suggesting
4 matches
Mail list logo