XOM API for Processing XML with Java

[Wolfgang Hoschek <whoschek AT lbl.gov>]

On Dec 5, 2004, at 9:36 AM, Elliotte Harold wrote:

> Wolfgang Hoschek wrote:
>
> > Can you be more specific? How and why would that remove other 
> > optimizations?
>
> In the current code base I've paid a lot of attention to making sure 
> each object carries around the minimum number of references it 
> possibly can, is not initialized until it is use,d and is initialized 
> to the minimum size it needs to be.

I know.

> This took quite a bit of work and profiling, all of which has to be 
> redone when you redesign the underlying structures.
>
> My initial attempt to remove the Attributes class increased memory 
> usage because saving a few bytes per element did not compensate for 
> losing the very carefully crafted ands measured optimizations in the 
> Attributes class. Eventually, I could reproduce these in the Element 
> class too, without the Attributes class, but it's not low-hanging 
> fruit.

I'm not sure I understand. The code logic remains exactly the same, 
there's no real diff other than that state moves into Element. Methods 
get inlined just like they did before, etc. I can send a patch if you 
like.

Wolfgang.