![]() | |
![]() |
| | Thread Tools | Search this Thread | Display Modes |
#11
| |||
| |||
|
|
"Greg Young" <druckdruckREMOVEgoose (AT) hotmail (DOT) com> wrote Chris it seems to me that you are NOT looking for the ability to put static methods in an interface but you are looking for a method to mark a method as stateless. The fact that a method is static does not make it stateless. Very true. I can (and do) write occasional static constructors, static variables, and other stateless no-no's. For the most part through, static means something pretty close to stateless. Getting back to the stateless issue C++ has a weak form of this in const. Yea, that's not quite what I'm looking for either though. I've done alot of C++ programming, and I do miss const and mutable in .Net, but I can get along without them. I do quite like readonly member variables, as they can only be written to in the constructor. The ability to mark that a method is stateless (and therefore thread safe) has been on the wish list of many for a long time. I would certatinly like this, although I still want to have it enforced by base classes and/or interface definitions. Ah well, perhaps C# 4.0 will have it... -- Chris Mullins, MCSD.Net, MCPD:Enterprise http://www.coversant.net/blogs/cmullins |
#12
| |||
| |||
|
|
Getting back to the stateless issue C++ has a weak form of this in const. |
![]() |
| Thread Tools | Search this Thread |
| Display Modes | |
| |