> I posted an answer to a question like 10 years ago before dynamic or anonymous types existed in .NET. It was valid and I later prefixed it to say another answ

> I posted an answer to a question like 10 years ago before dynamic or anonymous types existed in .NET. It was valid and I later prefixed it to say another answer is now correct but mine was correct for the version of .NET in question. > Still has people downvoting today. Aye that sucks. I have a PHP answer that is the accepted answer, but the PHP wonks got all up in arms about it because the immediate solution for the OP was to use the global keyword in their class method to get access to an array that's being created/modified in the global scope. I did caveat by letting them know this isn't a fantastic solution. But it looks like their app had a shedload of bigger problems that weren't going to be solved in my answer. I also miss the early days. Apropos my previous reply, I wasn't having a go at you, though re-reading it does seem that way, so I do apologise. I'd had a couple of wines and whenever stuff like this comes up I do feel slightly hacked off at all the effort I'd put into help build that empire (I was a <500 beta user, and was also a diamond mod). And all I got was a lousy mug and some crappy pens :)