This post originated from an RSS feed registered with .NET Buzz
by Duncan Mackenzie.
Original Post: Grant discusses Iterators...
Feed Title: Code/Tea/Etc...
Feed URL: /msdnerror.htm?aspxerrorpath=/duncanma/rss.aspx
Feed Description: Duncan is the Visual Basic Content Strategist at MSDN, the editor of the Visual Basic Developer Center (http://msdn.microsoft.com/vbasic), and the author of the "Coding 4 Fun" column on MSDN (http://msdn.microsoft.com/vbasic/using/columns/code4fun/default.aspx). While typically Visual Basic focused, his blogs sometimes wanders off of the technical path and into various musing of his troubled mind.
I've often had email exchanges and thought about posting them as blog entries... and now I've seen someone do it... and I have to say that it is a little hard to read (for the email part, start at the bottom and read up... which is normal for email, but not intuitive in a blog posting)... That difficulty is worth going through though because if you read the entire post you'll find out lots of useful info... :)
More thoughts on Iterators ... This got me thinking some more about iterators. The frameworks often use an int as a version field to detect when a collection has changed. This seems like a bit of overkill and isn't 100% correct because it does suffer from wrap-around (although that is almost entirely impossible short of malicious code). So I was wondering how you could write 100% correct code and still use an iterator, and have it be clean and maintainable code....