Skip to Content.
Sympa Menu

xom-interest - Re: [XOM-interest] Call for Votes: new name for ParseException

xom-interest AT lists.ibiblio.org

Subject: XOM API for Processing XML with Java

List archive

Chronological Thread  
  • From: Johan Strandberg <johan AT acm.org>
  • To: Elliotte Rusty Harold <elharo AT metalab.unc.edu>, XOM Interest List <xom-interest AT lists.ibiblio.org>
  • Cc:
  • Subject: Re: [XOM-interest] Call for Votes: new name for ParseException
  • Date: Sun, 20 Jul 2003 22:25:29 -0000

On Sun, 2003-07-20 at 14:19, Elliotte Rusty Harold wrote:
> [...] Possible new names for this class include:
>
> XMLParseException
> ParserException
> ParsingException

Yes, avoiding naming conflicts even across namespaces is good. Sooner or
later one ends up using the wrong one and the compiler won't have enough
context to help out with a syntax error.

ParserException and ParsingException are not good. I will never be able
to remember what I'm supposed to use, and the quick pop-up that my
editor (and many others) give, won't be of any help. It is like having
variables named itemCounter, itemsCounter, countedItems and countItems,
all in one program. Names needs to be distinct not only in spelling, but
in mnemonic space too. (My brain has too few hash-buckets as it it.)

XMLParseException is marginally better, but only until I run into a
conflict with org.some.xml.library.XMLParseExeption, and then we are
back where we started.

How about just using:

XOMParseException


--j




Archive powered by MHonArc 2.6.24.

Top of Page