On 2/3/11 1:30 PM, Tomek Sowiński wrote:
Andrei Alexandrescu napisał:
I'm not against replacement, but I'd be concerned about removal before a
replacement is available.
My problem is that the mere presence is reducing the likelihood of a
replacement coming about, in addition to the other liabilities.
Is anyone tasked with a replacement yet? I had to write an XML parser at some
point. It's plenty of work bringing up to industrial quality, so I'd have to
know that before I dive in.
Nobody that I know of. If you want to discuss design here while working
on it, that would be great. I could think of a few high-level requirements:
* works with input ranges so we can plug it in with any source
* works with all UTF widths (statically selectable)
* avoids where possible memory allocation (perhaps by offering
incremental access a la joiner())
* avoids often-called delegates in favor of alias functions
* is familiar in concept to people who've used today's successful XML
libraries
Andrei
