Comments on: Use self explicitly http://www.rubyfleebie.com/use-self-explicitly/ Because programming should be fun Thu, 15 Jul 2010 19:48:22 +0000 http://wordpress.org/?v=2.9.2 hourly 1 By: Frank http://www.rubyfleebie.com/use-self-explicitly/comment-page-1/#comment-852 Frank Thu, 09 Jul 2009 18:08:11 +0000 http://www.rubyfleebie.com/use-self-explicitly/#comment-852 Aljoscha, This could be a nice to have but at the same time... it could become annoying to see warnings everytime you declare a local variable that happens to have the same name of some instance method in the class hierarchy. I think that Ruby should force us to use "self" even for attribute readers. That way people would stop getting caught by this terrible gotcha. Thanks for you comment! Aljoscha,

This could be a nice to have but at the same time… it could become annoying to see warnings everytime you declare a local variable that happens to have the same name of some instance method in the class hierarchy. I think that Ruby should force us to use “self” even for attribute readers. That way people would stop getting caught by this terrible gotcha. Thanks for you comment!

]]> By: Aljoscha http://www.rubyfleebie.com/use-self-explicitly/comment-page-1/#comment-851 Aljoscha Thu, 09 Jul 2009 15:26:46 +0000 http://www.rubyfleebie.com/use-self-explicitly/#comment-851 We just got bitten by this. Now I ask myself (and you): Isn't there a way to make Ruby emit a warning when this kind of ambiguity occurs (When there is an attribute with that name?) Such a warning could help a lot. We just got bitten by this.
Now I ask myself (and you): Isn’t there a way to make Ruby emit a warning when this kind of ambiguity occurs (When there is an attribute with that name?) Such a warning could help a lot.

]]> By: I was just thinkin’… » Rails ActiveRecord callback gotcha! http://www.rubyfleebie.com/use-self-explicitly/comment-page-1/#comment-842 I was just thinkin’… » Rails ActiveRecord callback gotcha! Tue, 09 Jun 2009 14:09:29 +0000 http://www.rubyfleebie.com/use-self-explicitly/#comment-842 [...] @self.author_id=1@ as making a method call. Which makes perfect sense when you think about it see “Use self explicitly” for more details. (thanks to Craig Webster and Florian Gilcher, via Twitter for clearing this up [...] [...] @self.author_id=1@ as making a method call. Which makes perfect sense when you think about it see “Use self explicitly” for more details. (thanks to Craig Webster and Florian Gilcher, via Twitter for clearing this up [...]

]]> By: Ruby’s not ready - glyphobet • глыфобет • γλυφοβετ http://www.rubyfleebie.com/use-self-explicitly/comment-page-1/#comment-553 Ruby’s not ready - glyphobet • глыфобет • γλυφοβετ Mon, 07 Apr 2008 20:31:44 +0000 http://www.rubyfleebie.com/use-self-explicitly/#comment-553 [...] at least one case that requires self as an explicit reciever: when calling an attribute writer. Otherwise you’re just shadowing the attribute writer method locally. It’s not clear [...] [...] at least one case that requires self as an explicit reciever: when calling an attribute writer. Otherwise you’re just shadowing the attribute writer method locally. It’s not clear [...]

]]> By: James Crisp » Can you spot the bug? http://www.rubyfleebie.com/use-self-explicitly/comment-page-1/#comment-309 James Crisp » Can you spot the bug? Sat, 28 Jul 2007 09:20:24 +0000 http://www.rubyfleebie.com/use-self-explicitly/#comment-309 [...] The answer lies in the fact that Ruby requires an explicit self reference when using attribute writers (aka, property setters) within the class itself. This feels clunky to me, but for your information, here’s a rationalisation of the explicit self requirement. [...] [...] The answer lies in the fact that Ruby requires an explicit self reference when using attribute writers (aka, property setters) within the class itself. This feels clunky to me, but for your information, here’s a rationalisation of the explicit self requirement. [...]

]]> By: Gabe http://www.rubyfleebie.com/use-self-explicitly/comment-page-1/#comment-136 Gabe Tue, 17 Apr 2007 18:52:45 +0000 http://www.rubyfleebie.com/use-self-explicitly/#comment-136 This is one of those simple things I didn't know until I read Ruby for Rails. I highly recommend that book for illuminating numerous small details like this. Pickaxe is a great reference, but it glosses over a lot of those details in favor of a comprehensive picture of the language. Another one of these little gotchas is that referencing a non-existent local variable or method raises an exception, whereas a non-existent instance variable returns nil. This is one of those simple things I didn’t know until I read Ruby for Rails. I highly recommend that book for illuminating numerous small details like this. Pickaxe is a great reference, but it glosses over a lot of those details in favor of a comprehensive picture of the language.

Another one of these little gotchas is that referencing a non-existent local variable or method raises an exception, whereas a non-existent instance variable returns nil.

]]>