I have noticed in a lot of the mods i have looked at they seem to use this.field/method a lot e.g.

public void markDirty ()
    {
        buildTool(toolName);
        if (this.worldObj != null)
        {
            this.blockMetadata = this.worldObj.getBlockMetadata(this.xCoord, this.yCoord, this.zCoord);
            this.worldObj.markTileEntityChunkModified(this.xCoord, this.yCoord, this.zCoord, this);
        }
    }

(Example is from tconstruct)

I understand how it works but is it actually necessary? I would like to know because i dont use it almost at all in my mod except in constructors.

good practice in case a parameter name conflicts with an attribute (in which case it'd only set the variable in the scope of the function itself). if the variable names are different then it's not technically necessary but it still helps with remembering which scope you're dealing with (class or function)

Ok thanks i will start adding it from now on.

Hi

 

Largely a style choice, I don't think there's any consensus.  Personally I think it adds unnecessary clutter, and scope hiding is asking for trouble, so I only add it if my intentions are unusual and I want to make them obvious.  Others find it more clear to use this all the time.  Still others give their member variables a prefix eg m_blockMetadata.  If you're consistent I reckon it doesn't matter.

 

-TGG

 

 

Yeah I don't like it either style-wise. 

 

There are three cases I know of where you DO need the keyword this:

 

1. To be explicit that you're referring to an object field in the case where there is some other local or super variable with same name.  Like if you had an int field in your object called counter and then you had a for loop with its own index also called counter and you needed to access the object's counter field from within that loop.

 

2. To refer to the current object as a parameter to a method you're calling.  For example, if you're coding within a custom entity and adding ai tasks you would have:

tasks.addTask(0, new EntityAISwimming(this));

 

3. If you're calling a constructor of your object from within it.

    public ItemGoldenEgg() 
    {
	this("Golden Goose", 0xF5E16F, 0xF5F56F);
}
    
    public ItemGoldenEgg(String parEntityToSpawnName, int parPrimaryColor, int parSecondaryColor)
    {
        this.maxStackSize = 16; // same as regular egg
        this.setCreativeTab(CreativeTabs.tabMisc);
        colorBase = parPrimaryColor;
        colorSpots = parSecondaryColor;
    }

 

The general use of "this" all over the place is, as TheGreyGhost notes, arguable.  Some people think it makes it more readable, some like me and TGG think it makes it less readable (due to clutter).  But shouldn't create any issue with your code either way.

I don't like it either, but sometimes if I have trouble remembering the name of a variable or method "this." brings up the options and helps me out.  I go back and delete the 'this' at that point.  However, its not really hurting anything.  I just think it looks ugly.

In reality, 99%of the time when you see this in mods, its copy/pasta from vanilla code and people not knowing better.

But people are right there are cases where its NEEDED (Local variables shading class variables)

It's largely a style choice, however most 'modders' learn from decompiled code {horrible btw} which uses excessive 'this' to guarantee there are no shading issues.

Thank you all for your replies you have been very helpful!