>>>>> "Mark" == Mark Wielaard <[EMAIL PROTECTED]> writes:
>> assert type.getSort() == Type.OBJECT; Mark> Also note that this is a "dangerous" usage of assert. Inside the assert Mark> statement it does both a variable dereference, which could throw, and Mark> a method call, which might have all kinds of side-effects. That means Mark> that the code could execute completely different based on whether or not Mark> assertions are enabled or not. That seems a little silly, since we "know" that this method is simply an accessor. But fwiw I wouldn't mind if someone wanted to simply delete the assertion. Tom
