Comments on: Trivial accessors and uniform access http://www.adambyrtek.net/2008/02/09/trivial-accessors-and-uniform-access/ Skeptical Point of View Wed, 19 Nov 2008 11:38:45 +0000 http://wordpress.org/?v=2.3.3 By: Marcin Kaszyński http://www.adambyrtek.net/2008/02/09/trivial-accessors-and-uniform-access/#comment-333 Marcin Kaszyński Sun, 30 Mar 2008 18:12:00 +0000 http://www.adambyrtek.net/2008/02/09/trivial-accessors-and-uniform-access/#comment-333 There is a small bug in the Python version of Money: both getter and setter should use self._amount instead of self.amount. What are the other problems with this approach? There is a small bug in the Python version of Money: both getter and setter should use self._amount instead of self.amount.

What are the other problems with this approach?

]]> By: Tomek Paczkowski http://www.adambyrtek.net/2008/02/09/trivial-accessors-and-uniform-access/#comment-7 Tomek Paczkowski Sat, 09 Feb 2008 19:39:29 +0000 http://www.adambyrtek.net/2008/02/09/trivial-accessors-and-uniform-access/#comment-7 There is a good article about differences between Java and Python: <a href="http://dirtsimple.org/2004/12/python-is-not-java.html" rel="nofollow"> Python Is Not Java</a> by Phillip J. Eby. It's surely reading-worth for Java programmers wanting to learn Python. There is a good article about differences between Java and Python: Python Is Not Java by Phillip J. Eby. It’s surely reading-worth for Java programmers wanting to learn Python.

]]> By: Bartosz Bankowski http://www.adambyrtek.net/2008/02/09/trivial-accessors-and-uniform-access/#comment-6 Bartosz Bankowski Sat, 09 Feb 2008 19:07:05 +0000 http://www.adambyrtek.net/2008/02/09/trivial-accessors-and-uniform-access/#comment-6 It was an interesting article for me, as I didn't know about the UAP before. However, I don't agree with your assumptions: > But in Java you have to introduce getters > and setters from the very beginning, or it > will bite you back in the future. It > clearly contradicts with the DRY principle > and a preference for evolutionary design, > which discourages writing code that is > useless right now, but may (or may not) > be needed in the future. You say that I have to create getters and setters from the very beginning, while this is not true. I never do it. The very first time I create getter or setter is when I need to use it from my code. Described behavior would not only be against the DRY rule, but also could lead to broken encapsulation. > The whole problem boils down to the fact > that in Java you can’t apply the Uniform > Access Principle Which problem? From my point of view, the problem is not in a language, but in a design. It was an interesting article for me, as I didn’t know about the UAP before. However, I don’t agree with your assumptions:

> But in Java you have to introduce getters
> and setters from the very beginning, or it
> will bite you back in the future. It
> clearly contradicts with the DRY principle
> and a preference for evolutionary design,
> which discourages writing code that is
> useless right now, but may (or may not)
> be needed in the future.

You say that I have to create getters and setters from the very beginning, while
this is not true. I never do it. The very first time I create getter or setter is when I need to use it from my code.

Described behavior would not only be against the DRY rule, but also could lead to broken encapsulation.

> The whole problem boils down to the fact
> that in Java you can’t apply the Uniform
> Access Principle

Which problem? From my point of view, the problem is not in a language, but in a design.

]]> By: apohllo http://www.adambyrtek.net/2008/02/09/trivial-accessors-and-uniform-access/#comment-5 apohllo Sat, 09 Feb 2008 18:41:19 +0000 http://www.adambyrtek.net/2008/02/09/trivial-accessors-and-uniform-access/#comment-5 In Ruby instance attributes are private, but... there are two methods, namely instance_variable_get and instance_variable_set, which are public and allow "unrestricted" access to instance variables. So I think in Ruby the UAP is fully supported, but you CAN break it. In Ruby instance attributes are private, but… there are two methods, namely instance_variable_get and instance_variable_set, which are public and allow “unrestricted” access to instance variables. So I think in Ruby the UAP is fully supported, but you CAN break it.

]]>