R
Roedy Green
Consider this scenario.
You type a variable name and discover that it is undefined. You think
to yourself, "that name is correct, I must have forgotten to define
it".
You then insert the definition.
However, unbeknownst to you there are now TWO variable with very
slightly different names e.g.
filename and fileName or
firstGismoOnBlock vs firstGismoInBlock.
The compiler sometimes will not detect the error.
I have found the Eclipse reordering helps avoid this sort of problem.
The two variants will soon be pulled side by side whence the problem
becomes obvious. It can only hide if the two definitions are in
different parts of the class file.
The various outline views constantly expose the bare variable and
method names to view so that problems with naming or even two
legitimate similar variables warn you to rename to avoid ambiguity.
Some will smack me down saying, just be more careful. Don't make
mistakes. Deming, the father of quality control, points out such
exhortations are absolutely useless in achieving higher quality. You
need to change the environment of the worker to reduce errors.
Some would say, what sort of slob needs such a tool? Not a slob, a
perfectionist, who does not want even the slightest chance of an error
leaking through that could in theory be detected by automation.
--
Bush crime family lost/embezzled $3 trillion from Pentagon.
Complicit Bush-friendly media keeps mum. Rumsfeld confesses on video.
http://www.infowars.com/articles/us/mckinney_grills_rumsfeld.htm
Canadian Mind Products, Roedy Green.
See http://mindprod.com/iraq.html photos of Bush's war crimes
You type a variable name and discover that it is undefined. You think
to yourself, "that name is correct, I must have forgotten to define
it".
You then insert the definition.
However, unbeknownst to you there are now TWO variable with very
slightly different names e.g.
filename and fileName or
firstGismoOnBlock vs firstGismoInBlock.
The compiler sometimes will not detect the error.
I have found the Eclipse reordering helps avoid this sort of problem.
The two variants will soon be pulled side by side whence the problem
becomes obvious. It can only hide if the two definitions are in
different parts of the class file.
The various outline views constantly expose the bare variable and
method names to view so that problems with naming or even two
legitimate similar variables warn you to rename to avoid ambiguity.
Some will smack me down saying, just be more careful. Don't make
mistakes. Deming, the father of quality control, points out such
exhortations are absolutely useless in achieving higher quality. You
need to change the environment of the worker to reduce errors.
Some would say, what sort of slob needs such a tool? Not a slob, a
perfectionist, who does not want even the slightest chance of an error
leaking through that could in theory be detected by automation.
--
Bush crime family lost/embezzled $3 trillion from Pentagon.
Complicit Bush-friendly media keeps mum. Rumsfeld confesses on video.
http://www.infowars.com/articles/us/mckinney_grills_rumsfeld.htm
Canadian Mind Products, Roedy Green.
See http://mindprod.com/iraq.html photos of Bush's war crimes