Re: About using assertion
On 19 Mai, 15:38, Lew <no...@lewscanon.com> wrote:
On 05/19/2011 09:16 AM, Michal Kleczek wrote:
Lew wrote:
That is wrong. That needs to be checked with an 'if' if 'NaN' is no=
t a
legitimate input. 'assert' is not meant to correct things, only to =
make
sure
I totally agree with you.
that the correction is documented and proven. If 'assert' is turned=
off
in production, you still have the bug if you use 'assert' as the only
guard.
I was imprecise - just wanted to praise an example of "having confidenc=
e"
being sooo wrong and how having assertions (even though they look redun=
dant)
_may_ help you.
Totally correct.
Assertions are a signpost: HERE THERE BE AN INVARIANT!
When subtypes or refactored code violate the invariant, the assertion can=
help
catch it.
public class Foo
{
private Attribute attribute;
public void setAttribute( Attribute attr )
{
if ( attr == null )
{
throw new IllegalArgumentException( "null argument, dummy=
" );
}
attribute = attr;
assert attribute != null;
}
public Attribute getAttribute()
{
assert attribute != null;
return attribute;
}
}
public class Bar extends Foo()
{
public void setAttribute( Attribute attr )
{
attribute = attr;
Sorry for the nitpicking, but this cannot compile unless you make
"attribute" protected or package visible. But that in itself would be
a code smell IMHO. (Even though Java's std lib uses protected in
various places. But that's a completely different topic...)
}
}
The assertion will help reveal that class 'Bar' violated the invariant. =
In
production, the 'NullPointerException' (in the logs from 'getAttribute()'
clients) will trigger an investigation, which will include enabling asser=
tions
for the class that yields the value, and then the invariant checks will h=
elp
find the problem.
I think I get your point about the usage of assert here but we might
find a better example. In this particular case the NPE would catch
misbehaved sub class code anyway which must go through setAttribute if
the member variable remains declared "private" (my preferred
solution).
How about this as an example using template method pattern.
public abstract class Base {
/** Sub classes must override this and return an Attribute
* where {@link Attribute#getProperty()} returns something
* useful (!= null).
* @return an Attribute with Property, not null.
*/
protected abstract Attribute getAttribute();
/** This is the great algorithm this class is all about. */
public void theAlgorithm() {
final Attribute at = getAttribute();
/* We use individual asserts instead of && to easier find the
* violated rule. */
assert at != null;
assert at.getProperty() != null;
// now we can start working
System.out.println("Now this works: " +
at.getProperty().getLength());
}
}
Kind regards
robert