Hacker News Reader

Comment by mgrouchy | Hacker News Reader

Funny this ends up here. I was asking earlier on twitter today about whether there was a C# convention for naming private variables.

Seems that it is indeed _variablename , while I don't know if I like it, it would seem that it is more common then I thought and specifically mentioned in this article.

View on HN

The official .NET class design guidelines only cover public interface: http://msdn.microsoft.com/en-us/library/czefa0ke(VS.71).aspx

_privates is common, but in my experience at the largest of all C# shops, the explicit this.privates is more common. I use Resharper to enforce this style, but then again I use Resharper for every damn feature that wonderful wonderful magically tool provides.

Because Perl's OO stuff is screwed up and has now private/public/protected distinction I used a _ and __ convention for protected and private member variables.

e.g.

  $object->{this_is_public}
  $object->{this_is_protected_}
  $object->{this_is_private__}

There is also a trend to use variablename_ instead, a subtle change, but feels a bit better.

Reply on news.ycombinator.com