Bug 520 - Replacing nodes while iterating is broken
Summary: Replacing nodes while iterating is broken
Status: RESOLVED INVALID
Alias: None
Product: Class Libraries
Classification: Mono
Component: System.XML ()
Version: master
Hardware: PC Mac OS
: --- normal
Target Milestone: Untriaged
Assignee: Atsushi Eno
URL:
Depends on:
Blocks:
 
Reported: 2011-08-29 11:06 UTC by Alan McGovern
Modified: 2011-08-31 05:11 UTC (History)
2 users (show)

Tags:
Is this bug a regression?: ---
Last known good build:


Attachments
test app (675 bytes, text/plain)
2011-08-29 11:06 UTC, Alan McGovern
Details


Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.


Please create a new report on GitHub or Developer Community with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:
Status:
RESOLVED INVALID

Description Alan McGovern 2011-08-29 11:06:55 UTC
Created attachment 206 [details]
test app

Run the attached test program.

Under mono the following is printed:
Bar
Bar_
Baz
Bim

Under MS .NET the following is printed:
Bar
Baz
Bim
Bar_
Baz_
Bim_
Comment 1 Atsushi Eno 2011-08-31 01:58:07 UTC
It is a bug in .NET. XmlNodeList must be a *live* tree as in W3C DOM context. 
http://www.w3.org/TR/DOM-Level-2-Core/core.html#td-live 
http://msdn.microsoft.com/en-us/library/9abwaty7.aspx

When you remove *current* node from the node list, the *live* iteration is expected as what mono does. .NET fails to retrieve live nodes and returns nodes from the *dead* list.
Comment 2 Alan McGovern 2011-08-31 04:56:53 UTC
We could probably fix this by caching the current node in the iterator so if the current node is replaced, like in this example, the iterator uses the original one to walk to the next node. That'd resolve this bug and still maintain the required behaviour. Is this possible to implement?
Comment 3 Atsushi Eno 2011-08-31 05:11:51 UTC
I don't think it is possible. If current node is replaced, how can this go forward? The link to the next node is already lost.