RE: [DotGNU]System.Xml

[Simon Guindon]

I was lead to the same thing your saying, I did an increment inside of
ReadAttributeValue, it did make good progress, but it didn't solve
things.  And after much testing, which the modified testcase I attached
proves, that is not the problem.  .NET isn't auto-incrementing inside
ReadAttributeValue, its incrementing on the MoveNextAttribute.  The
problem is the true, false, true, false output, we need to figure out
when that false is decided apon because after every attribute read, its
executing a MoveNextAttribute, but PNET never executes that
MoveNextAttribute, hence the loop, because ReadAttributeValue() never
returns false.  I believe I have it narrowed down, I just don't know the
solution.

Take care,
Simon

-----Original Message-----
From: address@hidden [mailto:address@hidden 
Sent: July 14, 2003 2:42 PM
To: Simon Guindon
Cc: address@hidden
Subject: Re: [DotGNU]System.Xml


> if (attributeIndex < attributes.Count)
> {
>       value = attributes[attributeIndex].Value;
>       nodeType = XmlNodeType.Text;
>       return true;
> }
> else
> {
>       return false;
> }

You should also make sure to check for attributeIndex placement... != -1

if(attributeIndex < attributes.Count && attributeIndex > -1) { ... }

Make sure to remember that <?xml parsing is in a different area and
currently isn't handled like an element.  I've been hacking out this
exact problem in the newer parser, but again its not ready for primetime
so these bugs must be fixed.  I got stumped on this one because I was
wondering where we should increment, inside ReadAttributeValue()?
because it looks like gopal's test case will run a while loop on the
function waiting for it to turn false, but if its
stationary(attributeIndex is not
inc/dec) then it will always return true.  Something to think about...

_______________________________________________
Developers mailing list
address@hidden http://dotgnu.org/mailman/listinfo/developers