Comments on: Let Your Properties be Properties http://www.procata.com/blog/archives/2007/05/08/let-your-properties-be-properties/ PHP Programming, Web Development, PHP Advocacy and PHP Best Practices. Sun, 14 Mar 2010 11:08:56 -0400 http://wordpress.org/?v=2.8.6 hourly 1 By: MMF http://www.procata.com/blog/archives/2007/05/08/let-your-properties-be-properties/#comment-84325 MMF Sun, 23 Nov 2008 19:46:30 +0000 http://www.procata.com/blog/archives/2007/05/08/let-your-properties-be-properties/#comment-84325 Nice Nice

]]> By: pablo http://www.procata.com/blog/archives/2007/05/08/let-your-properties-be-properties/#comment-83516 pablo Sun, 16 Mar 2008 16:36:02 +0000 http://www.procata.com/blog/archives/2007/05/08/let-your-properties-be-properties/#comment-83516 Hi, you can have all the getXXX/setXXX methods without declaring them, just using the magic function __call and cutting the "get" or "set" part from the name of the method invoked and doing the $obj->XXX = value internally in __call. That's what I do in my projects. cheers, Pablo. Hi, you can have all the getXXX/setXXX methods without declaring them, just using the magic function __call and cutting the “get” or “set” part from the name of the method invoked and doing the $obj->XXX = value internally in __call. That’s what I do in my projects.

cheers,
Pablo.

]]> By: Sebas http://www.procata.com/blog/archives/2007/05/08/let-your-properties-be-properties/#comment-82602 Sebas Tue, 30 Oct 2007 11:21:58 +0000 http://www.procata.com/blog/archives/2007/05/08/let-your-properties-be-properties/#comment-82602 <blockquote> I'm strongly in favour of getFoo() / setFoo() because I think it's important to have a well-defined interface. </blockquote> How would you program this to an interface. Getters and setters are conventions, not interface implementations, or am I missing your point?

I’m strongly in favour of getFoo() / setFoo() because I think it’s important to have a well-defined interface.

How would you program this to an interface.
Getters and setters are conventions, not interface implementations, or am I missing your point?

]]> By: Wolkje.net Weblog » Blog Archive » Accessing properties in PHP objects http://www.procata.com/blog/archives/2007/05/08/let-your-properties-be-properties/#comment-82577 Wolkje.net Weblog » Blog Archive » Accessing properties in PHP objects Mon, 29 Oct 2007 09:20:49 +0000 http://www.procata.com/blog/archives/2007/05/08/let-your-properties-be-properties/#comment-82577 [...] I stumbled upon a weblog post of Jeff Moore on the way properties of objects should be accessed in PHP. Accidently, I thought a little about this problem myself last week because I’m working on a [...] [...] I stumbled upon a weblog post of Jeff Moore on the way properties of objects should be accessed in PHP. Accidently, I thought a little about this problem myself last week because I’m working on a [...]

]]> By: David http://www.procata.com/blog/archives/2007/05/08/let-your-properties-be-properties/#comment-81670 David Thu, 24 May 2007 17:39:03 +0000 http://www.procata.com/blog/archives/2007/05/08/let-your-properties-be-properties/#comment-81670 I understand the logic to this, but it's going to be more tedious as you get into larger applications with many classes vars and (of course) properties... For every var to be treated individually like that may be daunting. If you're writing an application that's just going to sit and function (little to no maintenance), then I don't know how worthwhile it'd be to use this method. Though for larger applications that undergo maintenance and upgrading/updating, I think that this is very acceptable, and might help avoid problems with making edits down the road. I understand the logic to this, but it’s going to be more tedious as you get into larger applications with many classes vars and (of course) properties… For every var to be treated individually like that may be daunting.

If you’re writing an application that’s just going to sit and function (little to no maintenance), then I don’t know how worthwhile it’d be to use this method. Though for larger applications that undergo maintenance and upgrading/updating, I think that this is very acceptable, and might help avoid problems with making edits down the road.

]]> By: developercast.com » Jeff Moore’s Blog: Let Your Properties be Properties http://www.procata.com/blog/archives/2007/05/08/let-your-properties-be-properties/#comment-81487 developercast.com » Jeff Moore’s Blog: Let Your Properties be Properties Thu, 10 May 2007 12:54:40 +0000 http://www.procata.com/blog/archives/2007/05/08/let-your-properties-be-properties/#comment-81487 [...] a recent post to his blog, Jeff Moore advocates the philosophy that, in your OOP application development, you [...] [...] a recent post to his blog, Jeff Moore advocates the philosophy that, in your OOP application development, you [...]

]]> By: PHPDeveloper.org http://www.procata.com/blog/archives/2007/05/08/let-your-properties-be-properties/#comment-81486 PHPDeveloper.org Thu, 10 May 2007 12:13:53 +0000 http://www.procata.com/blog/archives/2007/05/08/let-your-properties-be-properties/#comment-81486 <strong>Jeff Moore's Blog: Let Your Properties be Properties</strong> Jeff Moore’s Blog: Let Your Properties be Properties

]]> By: Chris http://www.procata.com/blog/archives/2007/05/08/let-your-properties-be-properties/#comment-81482 Chris Wed, 09 May 2007 10:53:37 +0000 http://www.procata.com/blog/archives/2007/05/08/let-your-properties-be-properties/#comment-81482 i am undecided if magic methods are a good thing. i am using them but they get quite messy if inheritance comes into play. mostly i end up writing protected setters to encapsulate them better and make sure that inheriting classes have a well defined interface to override a setter. how do you handle inheritance with your magic methods? i am undecided if magic methods are a good thing. i am using them but they get quite messy if inheritance comes into play. mostly i end up writing protected setters to encapsulate them better and make sure that inheriting classes have a well defined interface to override a setter.

how do you handle inheritance with your magic methods?

]]> By: Sebs http://www.procata.com/blog/archives/2007/05/08/let-your-properties-be-properties/#comment-81481 Sebs Wed, 09 May 2007 09:11:00 +0000 http://www.procata.com/blog/archives/2007/05/08/let-your-properties-be-properties/#comment-81481 the get/set pattern is that what i hate. its slow (function calls are slow) its obfuscating the code its so javaesk its ignoring the fact that there are the __get etc. methods so another one saying NO to the get/set schema the get/set pattern is that what i hate.
its slow (function calls are slow)
its obfuscating the code
its so javaesk
its ignoring the fact that there are the __get etc. methods

so another one saying NO to the get/set schema

]]> By: Joppe http://www.procata.com/blog/archives/2007/05/08/let-your-properties-be-properties/#comment-81480 Joppe Wed, 09 May 2007 07:30:49 +0000 http://www.procata.com/blog/archives/2007/05/08/let-your-properties-be-properties/#comment-81480 I don't understand what you're doing. If you make a class that's extensible then you're making a base class, or am i wrong? Do you mean that you use the possibility of PHP to set new (not existing) properties of a class? What is setXXX? Are you setting a property xxx of a class, is xxx an existing property or is it a new property, is xxx an object? How do you use it, $obj->setXXX( 'prop' , 'foo' ) ; ? I don’t understand what you’re doing.
If you make a class that’s extensible then you’re making a base class, or am i wrong? Do you mean that you use the possibility of PHP to set new (not existing) properties of a class?
What is setXXX? Are you setting a property xxx of a class, is xxx an existing property or is it a new property, is xxx an object?
How do you use it, $obj->setXXX( ‘prop’ , ‘foo’ ) ; ?

]]>