It seems worthwhile in a service-provider situation where you do not
wish to enforce use of $this in service consumers.
The service provider can impliment caller without modifying existing
code.
Semantically, it should be considered redundant to pass $this in a
method call. There should be
If the object needs to behave differently based on who called it, there's
already a very easy way to do that:
class A {
function foo() {
$b = new B();
$b->bar($this);
}
}
class B {
function bar($caller) {
if ($caller instance of A) {
// ...
}
}
}
That's also there
(Please direct me elsewhere if necessary, this is a feature request)
It would be handy to allow a method to behave differently based on who is
calling it.
the function I am looking for would essentially do this:
function getCaller(){
$bt = debug_backtrace();
return $bt[2]['objec
Michael Maclean wrote:
Hi,
Earlier on someone on IRC mentioned that ext/hash had no support for the
FNV-1 hash function
(http://en.wikipedia.org/wiki/Fowler-Noll-Vo_hash_function), so I
decided to have a go at adding it.
I've since updated the patch with some tests based on the ones in the
ori
On Wed, Sep 16, 2009 at 10:14:55AM +0100, Ian Tighe wrote:
> Hi. I hope this has been sent to the right place.
> I am using files that are mount.cif share files. My client is a samba linux
> box but acting as a client over cifs to an XP box (several in fact).
> I am descending the share recursive
Hi. I hope this has been sent to the right place.
I am using files that are mount.cif share files. My client is a samba linux box
but acting as a client over cifs to an XP box (several in fact).
I am descending the share recursively with opendir and readdir detecting files
( and of course direct
