Lee Qid wrote:
> Hi there,
> 
> and excuse me for butting in on this one, but the post just rung my alarm 
> bell.
> 
> Am I interpreting your post correctly? You want to implement your own
> XML parser.

No, I have already.

> Wouldn't that be like reinventing the wheel? There are tons of them
> out there - there's bound to be one that fits the requirements.

Yup, but not for my needs (why I implemented it in the first place).
They are all way too bloated for what I needed it for.

> The post also raises a few questions:
> What exactly do you want to improve on with the new parser?

See my other post:
4. The main reason I put time into it is to try get rid of the
occasional hicks I see when new terrain (along with new models) get
loaded at runtime. I was hoping that a faster XML parser might improve that.

> What's the talk about memory fragmentation about?

Sounds like you're asking something you don't know much about.
Anyway, the more the memory get fragmented (due to allocating en freeing 
memory sections), the harder is gets for the memory allocator to find a 
proper region so the longer it takes to get one. This can hurt runtime 
performance big time.
So, reducing memory fragmentation could improve execution speed.
(Unless you throw in massive amounts of internal memory off course)

This is exactly the reason why Firefox is using it's own memory manager 
code now (instead of relying on the one provided by the operating system)

Erik

------------------------------------------------------------------------------
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
Series Scanner you'll get full speed at 300 dpi even with all image 
processing features enabled. http://p.sf.net/sfu/kodak-com
_______________________________________________
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel

Reply via email to