[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [jdt-core-dev] Re: What should Eclipse compiler default settings be ?
|
It would also need to find all code where the variable may actually be
assigned (as opposed to read), so as to remove it.
I guess it would just need to discard the variable, and try recompiling,
see if it has unbound references for the same name, and fix these.
"Claude Knaus"
<Claude_Knaus@oti.c To: jdt-core-dev@xxxxxxxxxxx
om> cc:
Sent by: Subject: Re: [jdt-core-dev] Re: What should Eclipse compiler default
jdt-core-dev-admin@ settings be ?
eclipse.org
10/16/2002 06:06 PM
Please respond to
jdt-core-dev
There should be at least two entries for clearing the local variable.
One removing the variable only, and another removing the initializer (if
any) as well.
That said, I would be faster in selecting and deleting by hand rather than
waiting for Ctrl+1 to offer me
the choices and selecting the right one.
celek@xxxxxxxxxx
Sent by: To: jdt-core-dev@xxxxxxxxxxx
jdt-core-dev-admin@ecl cc:
ipse.org Subject: Re: [jdt-core-dev] Re:
What should Eclipse compiler default settings be
?
16.10.2002 17:45
Please respond to
jdt-core-dev
Ok,
so we may not run it minutes before the last build :-)
I still believe some code analyzer (don;t find the proper term) would be
good
I am ok with the warning if I can have some kind of options that says -
clean warning upon save, or some kind of Ctrl+1 that will clean the import
and remove the local variable
Don't know if I make myself clear ?
--
Christophe Elek
Eclipse.org (Platform Update)
(905) 413-3467
Wednesday, October 16, 2002 10:24 AM
To: jdt-core-dev@xxxxxxxxxxx
cc:
From: "Olivier Thomann" <Olivier_Thomann@xxxxxxx>
Subject: Re: [jdt-core-dev] Re: What should Eclipse compiler default
settings be ?
The problem is that bad code might hide bugs and therefore it should be
done directly at the beginning of the development cycle. Otherwise we might
not test the same version you used if you change everything at the end.
I think the warnings I recommand are not too strong.
Fixing the warnings earlier reduce the stress at the end of the cycle...
just before a release when you cannot change anything anymore and you
finally keep this useless pieces of code.
Olivier
_______________________________________________
jdt-core-dev mailing list
jdt-core-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/jdt-core-dev
_______________________________________________
jdt-core-dev mailing list
jdt-core-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/jdt-core-dev
