At 08:49 PM 3/10/2001 +0100, Andr Langhorst wrote:
When you say that people shouldn't use references because of performance
what do you mean? I think you are right in general but when you are
passing around objects you should use references. for example:
function foo($obj)
{
}
foo($myobject);
At 12:56 AM 3/10/2001 +0100, Andr Langhorst wrote:
Hi,
1) I am currently completing the php documentation to cover all
undocumented features and I have noticed that using a static method call
to the same class from on instanciated object exhibits the presence of the
instance within the static
There are no static functions in PHP. This syntax is used to call a
method of the parent. It can be used to call other methods and thus have
parent::foo();
If you remember, it has been implemented *after*
[classname]::[functionname]() ...
the wrong $this but I wouldn't document it.
At 01:30 AM 3/10/2001 +0100, Andr Langhorst wrote:
There are no static functions in PHP. This syntax is used to call a
method of the parent. It can be used to call other methods and thus have
parent::foo();
If you remember, it has been implemented *after*
[classname]::[functionname]() ...
I
I still don't understand what the problem is? What should be documented
is the right way to use these calls.
problem 1 : how do I call the "::" operator and how do I call what it
does if it is no static call.
problem 2 : the "bug" with incorrect $this I mentioned, it is at least
Right, and they weren't static functions either (this feature was
designed for calling parent/grandparent/etc methods). The way it's
designed is completely intentional.
ok. this makes sense now :)
andr
--
Andr Langhorstt: +49 331 5811560
[EMAIL PROTECTED] m: +49 173
