self

I can access a python function's attribute inside of function itself by below code: def aa(): print aa.__name__ print aa.__hash__ # other simliar However, if above aa() function is a template for write other code, say bb() , I have to write: def bb(): print bb.__name__ print bb.__hash__ # other simliar Is there a "pointer" similar to the self argument in a class method so I could write code like this? def whatever(): print self.__name__ print self.__hash__ # other simliar I searched and found someone said to use the class to solve this problem, but that may be a trouble to redefine all the

I was reading a Ruby book and came across this definition of the pseudo-variable self: self - receiver object of the current method Could someone break down that definition and explain what it means? I don't understand any of it. EDIT: I actually have a pretty good idea of what self is (and its applications) and I know how to search on Google. I was just wondering if someone could explain the definition I quoted. That specifically. Ruby and other languages (such as Smalltalk and Objective-C) prefer the term "message passing", whereas Java and C++ prefer "method invocation". That is, the "Java

In testing a getter/setter pair in a rails model, I've found a good example of behavior I've always thought was odd and inconsistent. In this example I'm dealing with class Folder < ActiveRecord::Base . Folder belongs_to :parent, :class_name => 'Folder' On the getter method, if I use: def parent_name parent.name end ...or... def parent_name self.parent.name end ...the result is exactly the same, I get the name of the parent folder. However, in the getter method if I use... def parent_name=(name) parent = self.class.find_by_name(name) end ... parent becomes nil, but if I use... def parent_name=

from what I understand of the self keyword, it simply refers to the current instance of the class. Isn't this the default behaviour at all times anyways? For example, isn't self.var_one = method(args) equivalent to just var_one = method(args) ? If so then what is the use of self? In most cases self.foo is indeed redundant because you can just write foo for the same effect, but in this case it is not and the self is required. var_one = method(args) will create a local variable called var_one , it will not call any method or do anything else to self . self.var_one = method(args) will call the

I have seen a fair amount of blogs & videos on Go and as far as I recall, none of the authors use 'self' or 'this' for the receiver variable when writing methods. However there seems to be a number of questions on stack overflow that do this, and it got me thinking about if this is misleading to name the variable 'self'? Reading the Spec for Method Sets does not provide any evidence either way (in my interpretation). I seem to recall finding somewhere that it was not really a self pointer, can anyone list evidence or provide reasoning either way, and if any problems/traps that might occur from