[jdom-interest] How to "crash" JDOM, part 1

[David W. Smiley]

> The right solution is for JDOM somehow to support both worlds.  Because
> if it doesn't, then someone (could be me) has an incentive to fork and
> write a version without all the checks that runs faster.  How to support
> both "sanity checking" and "non-sanity checking" version is the real
> trick.

--hence the need for the builder design pattern.  But it looks like it's
becoming too late for such a major change since beta5 is nearing.  The
change would mostly reflect implementation of existing classes and the
input classes.

-- David Smiley