More odd behavior – DynamicObject this time

I posted some sample code recently, for some tests with C# 4.0 dynamic. Now I’ve found a new interesting thing — perhaps this is also related to using beta 2 instead of the RC, again I’ll try this when I get around to it.

For a while there I thought there was some logic in this — after all, Fall could conceivably be an element that has to be “accessed” first, before it can be “executed”, like a property that returns an anonymous function or similar. But since the behavior seems to change with the surrounding code in the caller method, it looks much more like a bug… hopefully just in beta 2.

Yeah, I believe that – but I haven’t checked it. I lost interest in the exact reason when I saw that the behavior depends on a few lines of entirely unconnected code. I don’t expect this to be intended behavior anymore. Will keep this blog posted when I find out more.