Click here to Skip to main content

Welcome to the Lounge

For discussing anything related to a software developer's life but is not for programming questions. Got a programming question?

The Lounge is rated Safe For Work. If you're about to post something inappropriate for a shared office environment, then don't post it. No ads, no abuse, and no programming questions. Trolling, (political, climate, religious or whatever) will result in your account being removed.

Re: This vs. that

Nish Nishant5-Dec-14 8:41

5-Dec-14 8:41

I did some searching but could not find that any more. Looks like they don't have a single document any more. This was from several years back. Once you installed the StyleCop plugin (was not part of VS then), it would issue warnings when you accessed a member without prefixing this.

Regards,
Nish

Blog: voidnish.wordpress.com

Re: This vs. that

PIEBALDconsult5-Dec-14 9:24

5-Dec-14 9:24

Nish Sivakumar wrote:
StyleCop

Dead | X|

Re: This vs. that

Nish Nishant5-Dec-14 9:36

5-Dec-14 9:36

Heh

Smile | :)

Not everyone's cup of tea, I know.

Regards,
Nish

Blog: voidnish.wordpress.com

Re: This vs. that

Nish Nishant5-Dec-14 8:43

5-Dec-14 8:43

Managed to dig out the old StyleCop page :

http://stylecop.soyuz5.com/SA1101.html[^]

Could not locate the original full document, sorry.

Regards,
Nish

Blog: voidnish.wordpress.com

Re: This vs. that

Jeremy Falcon4-Dec-14 11:51

4-Dec-14 11:51

I've gone both ways, and both points are valid. I find myself using this a lot in JavasScript for some reason, but in C# I seldom do. For me, my biggest peeve is inconstancy in a project. So, looks like one of y'all are going to have to give in, or you could have him off'ed.

Jeremy Falcon

Re: This vs. that

Mark_Wallace4-Dec-14 12:05

4-Dec-14 12:05

I think it's tip 97 in the How to Make C# Look Like Java guide.

I wanna be a eunuchs developer! Pass me a bread knife!

Re: This vs. that

Popular

R. Giskard Reventlov4-Dec-14 13:02

R. Giskard Reventlov

4-Dec-14 13:02

this.Redundant

Re: This vs. that

Keith Barrow4-Dec-14 21:23

4-Dec-14 21:23

Errrm, this.

Alberto Brandolini:
The amount of energy necessary to refute bullshit is an order of magnitude bigger than to produce it.

Re: This vs. that

Agent__0074-Dec-14 21:37

4-Dec-14 21:37

Only assignment, call, increment, decrement, and new object expressions can be used as a statement. Smile | :)

Smile | :)

Your time will come, if you let it be right.

Re: This vs. that

PIEBALDconsult4-Dec-14 13:03

4-Dec-14 13:03

I do that. I prefer to type more up front and scratch my head less later.

That it honks off some members here is frosting on the cake. Badger | [badger,badger,badger,badger...]

Badger | [badger,badger,badger,badger...]

Re: This vs. that

Popular

_Maxxx_4-Dec-14 13:51

4-Dec-14 13:51

My preference is to never use this unless there is a reason to do so (like conflicting names).

My methods are small enough that it is rarely a problem to see what is local and what is a property

and anyway, properties begin with a Capital and locals don't.

For static methods I use the classname. option, as there is no other obvious differentiator. That said, I don't work with many classes with static methods, so not something I have formed a habit out of.

When I see

this.SomeProperty = this.SomeMethod(this.SomeOtherProperty)

I cringe, and think "this? What else?)

PooperPig - Coming Soon

Re: This vs. that

Slacker0074-Dec-14 23:12

4-Dec-14 23:12

_Maxxx_ wrote:
(like conflicting names)

Thumbs Up | :thumbsup:

Thumbs Up | :thumbsup:

Thumbs Up | :thumbsup:

Re: This vs. that

Super Lloyd4-Dec-14 15:38

4-Dec-14 15:38

I do that sometimes....
And I don't really care either way...
And sometimes it's necessary when function parameter has the same name as class field!

My programming get away... The Blog...
DirectX for WinRT/C# since 2013!
Taking over the world since 1371!

Re: This vs. that

Sanjay K. Gupta4-Dec-14 17:54

Sanjay K. Gupta

4-Dec-14 17:54

I do not care about these redundancy but, personally, I do not prefer these type of redundant code.

___ ___           ___ 
|__ |_| |\ |    | |_| \ /
__| | | | \| |__| | |  /

Re: This vs. that

Nareesh14-Dec-14 18:09

4-Dec-14 18:09

By that same reasoning, stop using any "using" and reference only via fully qualified "System.Windows.Forms.ListCtrl.Item item" Roll eyes | :rolleyes:

Roll eyes | :rolleyes:

who needs any shortening of a line, just buy BLACK FRIDAY 50" MONITOR THATS IT?

Re: This vs. that

Agent__0074-Dec-14 19:22

4-Dec-14 19:22

Nareesh1 wrote:
fully qualified "System.Windows.Forms.ListCtrl.Item item"

Even when you say "fully qualified", there is no such thing as "System.Windows.Forms.ListCtrl.Item".. Laugh | :laugh:

Laugh | :laugh:

Nareesh1 wrote:
who needs any shortening of a line

Oh the irony! Laugh | :laugh:

Laugh | :laugh:

Your time will come, if you let it be right.

Re: This vs. that

Sander Rossel5-Dec-14 2:38

5-Dec-14 2:38

Yep, I know.
But I prefer not to include any Namespaces, only class names (the class name should be clear enough anyway).
I understand that in the new version of C# you can create a using for a class so you can use its static members without specifying the class. It's already my least favourite feature!

C#

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

Re: This vs. that

Jörgen Andersson4-Dec-14 18:54

Jörgen Andersson

4-Dec-14 18:54

Whenever there is the slightest chance of ambiguity, otherwise i prefer to keep it short.

Wrong is evil and must be defeated. - Jeff Ello
(√-sh*t)²

Re: This vs. that

V.4-Dec-14 19:43

4-Dec-14 19:43

Unless I have a construct like:

C#

public class X{
  private int number;

  public X(int number){
    this.number = number;
  }
}

I rarely uses this.

V.

(MQOTD rules and previous solutions)

Re: This vs. that

R. Erasmus4-Dec-14 20:06

4-Dec-14 20:06

I would say to use the property assignment 'this' in the following scenario:

C++

void foo(int someValue)
{
  this.someValue = someValue;
  this.SomeMethod(AnotherClass.SomeMethod());
}

But not in the following scenario:

C++

void foo()
{
  someValue = 5;
  SomeMethod(5);
}

With ThisClass.SomeStaticMethod() I'd always use is as you did unless of course you are using the static method of the class you are working in, then I'd just use SomeStaticMethod.

"Program testing can be used to show the presence of bugs, but never to show their absence."

<< please vote!! >>

Re: This vs. that

Nagy Vilmos4-Dec-14 21:53

4-Dec-14 21:53

this is good and I use it normally. The fact that it seems to annoy some pooples just encourages me to use it more. Big Grin | :-D

Big Grin | :-D

Re: This vs. that

Slacker0074-Dec-14 23:14

4-Dec-14 23:14

such a trouble maker and non-conformist. Big Grin | :-D

Big Grin | :-D

Re: This vs. that

den2k884-Dec-14 22:39

4-Dec-14 22:39

"this." triggers any auto-completion or Intellisense in the world. Yes I'm lazy - I wouldn't train machines to do men's work if I wasn't Wink | ;)

Wink | ;)

Re: This vs. that

Freak305-Dec-14 1:46

5-Dec-14 1:46

If you just type one or two letters and then press Ctrl + Space, you would also get Intellisense and have to type even less. Wink | ;)

Wink | ;)

The good thing about pessimism is, that you are always either right or pleasently surprised.

Re: This vs. that

Sander Rossel5-Dec-14 2:33

5-Dec-14 2:33

I don't think you have to type anything at all...

C#

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

General News Suggestion Question Bug Answer Joke Praise Rant Admin

Use Ctrl+Left/Right to switch messages, Ctrl+Up/Down to switch threads, Ctrl+Shift+Left/Right to switch pages.