Re: [udk-dev] Thoughts on String Construction / Destruction Performance

2005-10-04 Thread Stephan Bergmann
Kay Ramme - Sun Germany - Hamburg wrote: Hi guys, Thorsten Behrens wrote: Eike Rathke [EMAIL PROTECTED] writes: A specialized parser could almost certainly be faster than the general SAX parser passing strings back and forth. I wouldn't do it with lex/yacc though, they're a nightmare to

Re: [udk-dev] Thoughts on String Construction / Destruction Performance

2005-10-04 Thread Kay Ramme - Sun Germany - Hamburg
Stephan Bergmann wrote: Kay Ramme - Sun Germany - Hamburg wrote: Hi guys, Thorsten Behrens wrote: Eike Rathke [EMAIL PROTECTED] writes: A specialized parser could almost certainly be faster than the general SAX parser passing strings back and forth. I wouldn't do it with lex/yacc though,

Re: [udk-dev] Thoughts on String Construction / Destruction Performance

2005-09-26 Thread Kay Ramme - Sun Germany - Hamburg
Hi guys, Thorsten Behrens wrote: Eike Rathke [EMAIL PROTECTED] writes: A specialized parser could almost certainly be faster than the general SAX parser passing strings back and forth. I wouldn't do it with lex/yacc though, they're a nightmare to maintain, and in case wrong code was

Re: [udk-dev] Thoughts on String Construction / Destruction Performance

2005-09-26 Thread Eike Rathke
Hi Thorsten, On Sat, Sep 24, 2005 at 23:18:24 +0200, Thorsten Behrens wrote: hm. I'd profile a larger test case beforehand - spirit is a recursive parser vs. yacc being table-driven. A valid concern. IMHO yacc _will_ be faster anyway, the question is just how much, and whether spirit would be

Re: [udk-dev] Thoughts on String Construction / Destruction Performance

2005-09-24 Thread Thorsten Behrens
Eike Rathke [EMAIL PROTECTED] writes: A specialized parser could almost certainly be faster than the general SAX parser passing strings back and forth. I wouldn't do it with lex/yacc though, they're a nightmare to maintain, and in case wrong code was generated, which can happen, you're almost

Re: [udk-dev] Thoughts on String Construction / Destruction Performance

2005-09-15 Thread Kay Ramme - Sun Germany - Hamburg
Hi Niklas, Niklas Nebel wrote: Kay Ramme - Sun Germany - Hamburg wrote: The calculation just gives, what the optimum (minimum) looks like. If the implementation does more string instantiations than calculated, than it is obviously not optimal (in this aspect) and the impact of string con- /

Re: [udk-dev] Thoughts on String Construction / Destruction Performance

2005-09-14 Thread Kay Ramme - Sun Germany - Hamburg
Hi Niklas, Niklas Nebel wrote: Taking an attribute name as an example, with the SAX interface inbetween, the via callbacks part looks (roughly) like this: The name is copied into a vector for the XAttributeList implementation, copied again for two getNameByIndex calls (one to look for

Re: [udk-dev] Thoughts on String Construction / Destruction Performance

2005-09-13 Thread Eike Rathke
Hi Kay, On Tue, Sep 13, 2005 at 17:38:52 +0200, Kay Ramme - Sun Germany - Hamburg wrote: investigating especially into constructiondestruction and suggesting a slightly modified variant, with improved behavior. So, if you have some time left, I would like to get your feedback ;-). Thank