The Lounge - CodeProject

BillWoodruff5-Dec-14 1:59

5-Dec-14 1:59

It has become a habit for me to use 'this,' to type in access modifiers even when not required, and to never create duplicate names, but, over the last two years, I have transitioned to using 'var freely which I know causes some people to break out in a poison sweat.

I don't think these are particularly "bad" habits, but they are not any saving-grace of poor-quality design, or coding, either. At best, a syntactic sugar that may contribute to maintainability and future re-use ? But, I work alone, not in a team-setting.

If (gods forbid) I was managing a commercial software dev team, oh yeah, I'd plump for standards.

«OOP to me means only messaging, local retention and protection and hiding of state-process, and extreme late-binding of all things. » Alan Kay's clarification on what he meant by the term "Object" in "Object-Oriented Programming."

Re: This vs. that

ZurdoDev5-Dec-14 2:08

ZurdoDev

5-Dec-14 2:08

Interesting that a lot of people do use this. I did not expect that. $Shucks | :-\$

I don't like it. It just clutters up with extra code that is unnecessary. Sniff | :^)

There are only 10 types of people in the world, those who understand binary and those who don't.

Re: This vs. that

Sander Rossel5-Dec-14 2:33

Sander Rossel

5-Dec-14 2:33

BillWoodruff wrote:
At best, a syntactic sugar

Almost agreed.
The var keyword can actually be quite dangerous as I have witnessed a few times myself.
I work with Entity Framework a lot, which uses IQueryable to create queries that run on the database and return a result as IEnumerable that can be used in your application. Interface-wise there is little difference between IQueryable and IEnumerable, but the function of the two differs greatly! A few times I changed my IQueryable to IEnumerable and nothing broke, because the IQueryable was declared using var. The type of my variable just 'silently' changed to IEnumerable and all of a sudden my app wouldn't perform very well. Thing is, in order to create an IEnumerable the query was executed on the database. This was supposed to happen a few lines later, but because I put a ToList() function somewhere in between this was done to early. All my filter functions were done on the in-memory collection instead of the database.
Of course you'd also have this problem if you declared your IQueryable as IEnumerable (an IQueryable IS an IEnumerable), but at least you'd explicitly choose to define it as such.

I haven't seen this problem with other .NET interfaces, probably because none of them are so common and so costly as IQueryable, but I could imagine it happening when working with Streams or some such base class which has a few subclasses that do different things.

My blog[^]

public class SanderRossel : Lazy<Person>
{
   public void DoWork()
   {
      throw new NotSupportedException();
   }
}

Re: This vs. that

User 48350475-Dec-14 7:50

User 4835047

5-Dec-14 7:50

I have noticed in Android (and Java generally) they often prefix with m like mSomeMemberVariable instead of using this.

maybe it depends on the IDE if it has a good IntelliSense.

modified 20-Oct-19 21:02pm.

Visual Studio Community Edition now?

Jeremy Falcon4-Dec-14 9:10

Jeremy Falcon

4-Dec-14 9:10

In the world of free VS, first there was the Express edition, which lacked things like a resource editor (for unmanaged code), etc. Anyone know what the deal is with the Community edition? Is it still gimped somehow? The sales pitch says it has more to it than the Express edition, but doesn't say what exactly.

I won't install it since I have 2013 Ultimate, but my MSDN sub expired and I really don't feel like getting a new one when VS 2015 hits the scene.

Jeremy Falcon

Welcome to the Lounge