Re: Exception handling
In article <hf5tdc$bmg$1@news.albasani.net>, noone@lewscanon.com says...
Pitch wrote:
- exception chaining is nothing more than a reference to the root cause,
thus they have no functional purpose per se, unless we make use of those
references
Lew wrote:
Not sure what your point is here. No reference anywhere in programming has a
"functional purpose per se, unless we make use of those references". The
program itself doesn't have a "functional purpose per se, unless we make use
of" it. The definition of "functional" is "we make use of it".
Pitch wrote:
I will set a few examples where this is not so:
For example, take the length property of a string or an array. It is set
internally when the string is created. It is also used for various
calculations internal to String class.
But we do make use of that property. That's why it's exposed to the
programmer. This does not refute the notion that "functional per se" is
equivalent to "we make use of it".
Also, File class. Several properties like length, lastModified,
getParent, isHidden... are set when the object is created.
I still don't see what you mean. These properties have a functional purpose,
and we make use of them.
Also, URL class and itd getUserInfo is set automatically and is used by
several other classes.
Again, have a "functional purpose per se" and "we make use of them".
Also, class Thread has getPrority, getState that are also used
internally.
Ditto.
You will see that all those properties are set internally and used by
the class or by some other class in the framework. I say they have their
purpose.
This does not refute the notion that "functional" and "useful" are equivalent.
But the cause property of an exception is set by the programmer and used
by the programmer so it's a simple helper property. Something like
That makes it not functional, or somehow implies that we don't make use of it?
"Tag" or "Data" in some other languages and framework. It's not
something that will change the behaviour of the class or try-catch block
or enything in the whole JVM.
But it is something useful for a programmer.
By your reasoning, we should never use any property that has a 'setX()' method.
--
Lew