On Tue, Apr 09, 2002 at 12:23:57PM +0300, Zeev Suraski wrote:
For the record, the advantages and disadvantages of variable name
constructors were clear from day one,
Nonetheless they were seriously broken in PHP 3, and
class __get {
function __get() {
echo I am a constructor\n;
}
}
At 12:38 09/04/2002, Kristian Koehntopp wrote:
On Tue, Apr 09, 2002 at 12:23:57PM +0300, Zeev Suraski wrote:
For the record, the advantages and disadvantages of variable name
constructors were clear from day one,
Nonetheless they were seriously broken in PHP 3,
How? I really don't remember
At 10:05 AM 4/5/2002, Stig S. Bakken wrote:
Recommendation:
If overload() indeed supports variably named callback functions
such as __get_x(), support for this should be removed in order
to avoid a number of possible inconsistencies and namespace
pollution.
I don't particularly mind
Stig S. Bakken wrote:
Well, aggregate and MI are for solving different
problems, basically aggregate is for customizing
objects at runtime, while MI is done at compile time.
You are right, these are different. I had a longer mail on
types and classes, and how type == class is not true in
Kristian Köhntopp wrote:
In fact, setters, getters and wrappers provide a great
policy-agnostic mechanism to introduce policies of the
implementors choosing.
A final note: Sebastian told me that in ZE 2, constructors and
destructors have a fixed name like __construct() and
__destruct(). If
I have several observations regarding the newly implemented
aggregate() und overload() extensions. Depending on the
correctness of these observations you may want to reconsider the
inclusion of these extensions in the current build of PHP.
The following has not in its entirety verified in the
Recommendation:
If overload() indeed supports variably named callback functions
such as __get_x(), support for this should be removed in order
to avoid a number of possible inconsistencies and namespace
pollution.
Yes it does support it. No it shouldn't be removed. Why not explain
On Thu, Apr 04, 2002 at 03:06:30PM -0800, Shane Caraveo wrote:
Recommendation:
If overload() indeed supports variably named callback functions
such as __get_x(), support for this should be removed in order
to avoid a number of possible inconsistencies and namespace
pollution.
On 05/04/02, Kristian Koehntopp [EMAIL PROTECTED] wrote:
Observation:
aggreate and friends break the introspection in PHP, and may
interfere with serialization and sessions.
This is, because
get_class($obj) returns Origclass, and no trace of Classname.
Also, $obj is_a() Origclass, but not
Kristian Koehntopp wrote:
On Thu, Apr 04, 2002 at 03:06:30PM -0800, Shane Caraveo wrote:
Recommendation:
If overload() indeed supports variably named callback functions
such as __get_x(), support for this should be removed in order
to avoid a number of possible inconsistencies and namespace
On Fri, 2002-04-05 at 00:43, Kristian Koehntopp wrote:
I have several observations regarding the newly implemented
aggregate() und overload() extensions. Depending on the
correctness of these observations you may want to reconsider the
inclusion of these extensions in the current build of
11 matches
Mail list logo
