IEnumerator and Foreach

I wanted to write a simple post about List enumeration and suddenly realise that here we as developers, are about to enter a pradigm shift. No longer is the default to develop for a single processor, threading will not be something that clever programs use. Almost everything is going to require scaling and queuing.  Why? Well here comes Core Duo. Two processors on a single piece of silicon. In fact I even read that servers are going to be offered with four Core Quad Chips. Welcome to the “many core” era.

I almost always use foreach for all list processing. Of course as we move into a many core world the standard concept of foreach just wont cut it anymore. Consider the following.

foreach (Data x in List<Data> list)

That just doesn’t take advantage of this extra power. It keeps all the processing on a single thread on a single Core of a single CPU. Looking for bottlenecks, start right there. Of course the reason we use this is because of its simplicity. Everyone can read this. It makes sense.

However there is an answer, and as usual it isn’t anything new. In fact it is the GoF Visitor pattern, and it’s already it the code above (sorry must stop cheating).

By defining the operation that we want to perform outside of the loop, in this case Action.Do(x); then we allow ourselves the opportunity to change the loop.

foreach (Data x in List<Data> list)

Which only leaves us with one problem? How do we know when they are all finished?

I think just missed my own point here. Why? Well this is exactly the same thing that Eric Sink wrote about in response to Joels post


Leave a Reply

Please log in using one of these methods to post your comment: Logo

You are commenting using your account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s