XOM API for Processing XML with Java

[Elliotte Harold <elharo AT metalab.unc.edu>]

Asgeir Frimannsson wrote:
> Hi,
>
> In the method nu.xom.UnicodeUtil.decompose(..) (Xom 1.2b) there is a
> 1900ish-levels nested if-else statement that causes my Eclipse java editor
> to crash when opening the file. Yes, I know it's not a XOM-fault, but I
> thought I'd throw it on the list anyway...
>
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=206697

This has been a known bug in Eclipse for a while and I've reported it 
before:

https://bugs.eclipse.org/bugs/show_bug.cgi?id=154047


> As a quick sidenote, the decompose method can be very easily refactored into
> (IMO) a much cleaner switch() statement rather than the overly long if-else
> statements (I have no idea if this also has performance improvements?)...
> That's at least how I stopped my Eclipse from crashing :)

Interesting. My recollection is that that's how this method started. 
However that failed for other reasons related to maximum method size. 
It's been a while since I looked at this issue though, so I may be 
misremembering or something else related may have changed.

--
Elliotte Rusty Harold  elharo AT metalab.unc.edu
Java I/O 2nd Edition Just Published!
http://www.cafeaulait.org/books/javaio2/
http://www.amazon.com/exec/obidos/ISBN=0596527500/ref=nosim/cafeaulaitA/