Wait until they hear that CO has only half of the poisonous oxygen....

The most likely reason (assuming there really was a reason) is that you wanted to return a completely _different_ array to the caller vs just mutating the contents of the passed array from within the callee.

Surely the current nomenclature is "men of fighting age" ! Have to admit, it never occurred to me they might be talking about COD ! ;-)

Indeed - or "take the (500 lines of unstructured) output from that last command and turn them into a CSV file with these columns..."

I mean imagine being in the audience for this thing and NOT raising your hand at the end to politely ask "dude - wtf are you on?"

Admittedly, this is more of a terminal feature but still... :-)

Oh.. and to answer your question.. very _very_ much against them.

Even assuming (optimistically) a majority of these are bots and troll farms it's depressing that we're in an environment where people can post this kind of stuff. They won't win but we need to take it seriously.

Would be genuinely interested in your thoughts if you do. I used it a long time ago on some mega-refactoring projects and liked what it could do but can't really justify the expense for day-to-day development

C# expression trees to start inserting Excel formulae ! ;-)

Kind of neat if you're dealing repeatedly with the same data shapes or using excel to persist data you want to operate on with code. That's a fairly unusual case where I'm from but I may well be in a minority. I guess the other question is where does this end ? I mean you could use...

True - though you then have the overhead of having to decode the assembly. A couple of tools that _might_ help though I'm skeptical at this scale.. Resharper and NDepend. Both paid but with free trials. NDepend is probably close to doing what you want.

In a day? Tricky, but a blunt-force approach would be to build a simple grep-like tool to look for class definitions and then count callsites for their constructors. That would at least give a "way in" for identifying things that might be moved easily or conversely have high dependent count.

If you're interested, drop me a line here over on the project discussions page...

github.com/NeilMacMulle...