The std.xml module contains several bugs that need to be fixed. The most important one is that the parser fails to parse empty elements (IE elements that use the <tag name="value" /> format). I'd like to report this bug to the modules' maintainer, but I don't know who to contact. (This is an old bug - it's been around for at least a year and I'm surprised that it has not been fixed).

llee Wrote:

> The std.xml module contains several bugs that need to be fixed. The most important one is that the parser fails to parse empty elements (IE elements that use the <tag name="value" /> format). I'd like to report this bug to the modules' maintainer, but I don't know who to contact. (This is an old bug - it's been around for at least a year and I'm surprised that it has not been fixed).

I should also point out that the std.xml module does not have support for namespaces.

llee wrote:
> The std.xml module contains several bugs that need to be fixed. The most important one is that the parser fails to parse empty elements (IE elements that use the <tag name="value" /> format). I'd like to report this bug to the modules' maintainer, but I don't know who to contact. (This is an old bug - it's been around for at least a year and I'm surprised that it has not been fixed).

According to Andrei, std.xml is in line for a complete rewrite.

http://www.digitalmars.com/webnews/newsgroups.php?art_group=digitalmars.D&article_id=93547

-Lars

Lars T. Kyllingstad wrote:
> llee wrote:
>> The std.xml module contains several bugs that need to be fixed. The most important one is that the parser fails to parse empty elements (IE elements that use the <tag name="value" /> format). I'd like to report this bug to the modules' maintainer, but I don't know who to contact. (This is an old bug - it's been around for at least a year and I'm surprised that it has not been fixed).
> 
> According to Andrei, std.xml is in line for a complete rewrite.
> 
> http://www.digitalmars.com/webnews/newsgroups.php?art_group=digitalmars.D&article_id=93547 

Yes, I think that will be necessary. Any volunteers? :o)

Andrei

Andrei Alexandrescu wrote:
> Lars T. Kyllingstad wrote:
>> llee wrote:
>>> The std.xml module contains several bugs that need to be fixed. The most important one is that the parser fails to parse empty elements (IE elements that use the <tag name="value" /> format). I'd like to report this bug to the modules' maintainer, but I don't know who to contact. (This is an old bug - it's been around for at least a year and I'm surprised that it has not been fixed).
>>
>> According to Andrei, std.xml is in line for a complete rewrite.
>>
>> http://www.digitalmars.com/webnews/newsgroups.php?art_group=digitalmars.D&article_id=93547
> 
> 
> Yes, I think that will be necessary. Any volunteers? :o)
> 
> Andrei

There is already a high-performance one in Tango.  There must be some way to avoid duplicating effort.

Daniel Keep wrote:
> 
> Andrei Alexandrescu wrote:
>> Lars T. Kyllingstad wrote:
>>> llee wrote:
>>>> The std.xml module contains several bugs that need to be fixed. The
>>>> most important one is that the parser fails to parse empty elements
>>>> (IE elements that use the <tag name="value" /> format). I'd like to
>>>> report this bug to the modules' maintainer, but I don't know who to
>>>> contact. (This is an old bug - it's been around for at least a year
>>>> and I'm surprised that it has not been fixed).
>>> According to Andrei, std.xml is in line for a complete rewrite.
>>>
>>> http://www.digitalmars.com/webnews/newsgroups.php?art_group=digitalmars.D&article_id=93547
>>
>> Yes, I think that will be necessary. Any volunteers? :o)
>>
>> Andrei
> 
> There is already a high-performance one in Tango.  There must be some
> way to avoid duplicating effort.

Unfortunately I'm not seeing any. Besides, it would be great if phobos' xml would work with ranges.

Andrei

Andrei Alexandrescu:
>Unfortunately I'm not seeing any.<

There's a simple solution, future D2 programmers will have both libs installed, so they will just use the Tango XML reader. So the best solution is to remove the XML reader from Phobos. The idea is to remove most inter-library redundancy. The sooner such problem is solved, the better it will be for D2.


>Besides, it would be great if phobos' xml would work with ranges.<

Translated, it becomes:
"Besides, it would be great if tangos' xml would work with ranges.". I guess Tango2 will use ranges.

Bye,
bearophile

On 2009-07-28 10:09:04 -0400, Andrei Alexandrescu <SeeWebsiteForEmail@erdani.org> said:

>>> Yes, I think that will be necessary. Any volunteers? :o)
>>> 
>>> Andrei
>> 
>> There is already a high-performance one in Tango.  There must be some
>> way to avoid duplicating effort.
> 
> Unfortunately I'm not seeing any. Besides, it would be great if phobos' xml would work with ranges.

I started something which could be used as a replacement of std.xml. Once it's a little more ready, I could contribute it to Phobos. It includes two tokenizer APIs (a templated callback tokenizer and a range tokenizer), and one DOM (not really based on the W3C DOM). The goal is to support all of XML at the tokenizer level, but skipping the internal subset of the doctype in the DOM.

Currently, the range API would be more useful if there was a way to switch on the type of an Algebraic.

-- 
Michel Fortin
michel.fortin@michelf.com
http://michelf.com/

Michel Fortin wrote:
> On 2009-07-28 10:09:04 -0400, Andrei Alexandrescu <SeeWebsiteForEmail@erdani.org> said:
> 
>>>> Yes, I think that will be necessary. Any volunteers? :o)
>>>>
>>>> Andrei
>>>
>>> There is already a high-performance one in Tango.  There must be some
>>> way to avoid duplicating effort.
>>
>> Unfortunately I'm not seeing any. Besides, it would be great if phobos' xml would work with ranges.
> 
> I started something which could be used as a replacement of std.xml. Once it's a little more ready, I could contribute it to Phobos. It includes two tokenizer APIs (a templated callback tokenizer and a range tokenizer), and one DOM (not really based on the W3C DOM). The goal is to support all of XML at the tokenizer level, but skipping the internal subset of the doctype in the DOM.
> 
> Currently, the range API would be more useful if there was a way to switch on the type of an Algebraic.

But *why* use or make another one when the Tango one is already excellent? :(

On Tue, Jul 28, 2009 at 12:23:50PM -0300, Ary Borenszweig wrote:
> But *why* use or make another one when the Tango one is already excellent? :(

Copyright.

-- 
Adam D. Ruppe
http://arsdnet.net