, evildictaitor wrote

*snip*

Only one method would be created anyway. The only time multiple copies of a method can end up in memory is if either:

a) The method appears in two different assemblies

b) The method is generic and is used more than once with different generic parameters.

For example, the code for object.ToString() only appears only once in memory, despite that it is an instance method on every object that you create.

Sven is right - static variables are the thing to watch out for. Static methods which don't have static variables associated with them are perfectly fine and have no problems.

 

yeah that's right ----  i was recalling some code that had static vars and was called in a multi threaded app .... not fun finding randomly corrpupted data and then finding where and how that happened.