On Wed, 2003-07-02 at 13:24, Andi Gutmans wrote:
> I definitely prefer setXXX()/getXXX() functions over property overloading.
>
> Andi
I agree, but I am usually of the mindset that all properties should be
private, and should always have accessors (unless of course there is a
performance issue wi
On Wed, 2003-07-02 at 14:24, Andi Gutmans wrote:
> At 10:37 AM 2/7/2003 -0400, l0t3k wrote:
> >IIRC there was an informal consensus to use studlyCaps as the official
> >userland convention for OOP extensions (*) (leaving aside the case
> >insensitivity of the language.)
> >my question now concerns
At 10:37 AM 2/7/2003 -0400, l0t3k wrote:
IIRC there was an informal consensus to use studlyCaps as the official
userland convention for OOP extensions (*) (leaving aside the case
insensitivity of the language.)
my question now concerns accessors. should we prefer properties over
propertyGet()/prope
IIRC there was an informal consensus to use studlyCaps as the official
userland convention for OOP extensions (*) (leaving aside the case
insensitivity of the language.)
my question now concerns accessors. should we prefer properties over
propertyGet()/propertySet() accessor functions ? would havin
