Provide performance data that backs this up, before saying "there can be quite a performance penalty".
Speculation is not data. Debug builds are not release builds. -- arlie -----Original Message----- From: Moderated discussion of advanced .NET topics. [mailto:[EMAIL PROTECTED] On Behalf Of Urs Eichmann Sent: Tuesday, October 21, 2003 10:34 AM To: [EMAIL PROTECTED] Subject: Re: [ADVANCED-DOTNET] Do properties need a 'holder' keyword? > Also, some ams have rules. Our rules say: NO PUBLIC VARIABLES. NEVER. Thomas, IMHO This is a good rule - as long as it applies to public classes only. But if the classes are private to your assembly, I don't see the point of not having public members. After all, there can be quite a performance penalty if you use properties vs. Member variables. Urs =================================== This list is hosted by DevelopMentorR http://www.develop.com NEW! ASP.NET courses you may be interested in: 2 Days of ASP.NET, 29 Sept 2003, in Redmond http://www.develop.com/courses/2daspdotnet Guerrilla ASP.NET, 13 Oct 2003, in Boston http://www.develop.com/courses/gaspdotnet View archives and manage your subscription(s) at http://discuss.develop.com =================================== This list is hosted by DevelopMentorŪ http://www.develop.com NEW! ASP.NET courses you may be interested in: 2 Days of ASP.NET, 29 Sept 2003, in Redmond http://www.develop.com/courses/2daspdotnet Guerrilla ASP.NET, 13 Oct 2003, in Boston http://www.develop.com/courses/gaspdotnet View archives and manage your subscription(s) at http://discuss.develop.com
