Hi, > While you can make that argument for the Interface, the 'm_' prefix is > necessary in order to write .NET code that is portable between C# and > languages that do not support a "_" prefix for class level fields. Hence, > the "m_" (a hold over from when the 'm' denoted 'module')
or don't try to denote class level variables as being 'special' at all with either _ or m_ prefix? It seems to be a particular trait of MS development practice to use this code convention and personally I've never understood the reasoning behind it. Thanks, Kev --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
