LB>> But is it a reason to prevent *good* coders (i don't argue here i'm
LB>> one) from using it disabling a feature ?
Yes, sometimes it is a reason, if it's reasonably hard to do right.
LB>> > b) put all the variable handling on the user (you will have to check
LB>> > *each* access to the class
First of all, thank you for taking time to awser my last post.
> I don't think "more magic" is neccessarily good thing.
Good point, it's sometimes hard to find out what ten simple lines of
code do (in any language) due to obscure or missing documentation and
strange coding conventions.
But is it
LB>> The way python handle this is just fine and allow much more code magic
LB>> in classes.
I don't think "more magic" is neccessarily good thing.
LB>> The python rule : if we have a __get, __set, __call, we use it. no
LB>> more no less.
This will:
a) slow down *a lot* any class that has acce
Well may be i'm the only one (hard to say as nobody talk about this) but
i don't agree with accessors design, i allready posted a mail to Andrei
a month ago (may be lost, may be the wrong person) and i try here as
i'm sure someone will explain me 'why this design'.
Comment found in zend_object_
