Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Microsoft launches new open source codeplex foundation
Message
 
To
01/10/2009 11:25:28
General information
Forum:
Visual FoxPro
Category:
Other
Miscellaneous
Thread ID:
01424841
Message ID:
01427139
Views:
74
>
>I also go way back when it comes to naming fields for properties ... I prefer to use the "m_" convention. So, your example would look like this for me:
>
>
>public string SomeProperty
>{
>   //////
>}
>private string m_SomeProperty;
>
>
>I also dislike the variation of this that seems to be quite popular and that is just using the underscore, so it becomes:
>
>
>public string SomeProperty
>{
>   //////
>}
>private string _SomeProperty;
>
>
>I dunno ... it just seems harder to read. But maybe that's just me.
>

Not just you. I use the m_ prefix and I'm not much of a fan of just an underscore prefix. In C/C++ it seemed to become a war, first _something then __something, then ___something and, depending on the font, it is nearly impossible to tell how many underscores there are.
-Paul

RCS Solutions, Inc.
Blog
Twitter
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform