I think you can use reflection [1] to block the hooks from using & in their
parameter lists. This way the clients must use & to pass a reference. This
is definitely possible for function/method callbacks [2], but I'm not sure
about 5.3 closures [3].
David
[1] http://www.php.net/manual/en/reflecti
t;
> >echo is_multiscoped($jim); //False
> >
> >getJam($jim);
> >
> >
> >?>
> >
> >On Tue, Feb 1, 2011 at 7:12 PM, Tommy Pham wrote:
> >
> >> > -Original Message-
> >> > From: Brad Lorge [mailto:b...@lorge.com.au]
>
uot;nothing special";
>
>echo is_multiscoped($jim); //False
>
>getJam($jim);
>
>
>?>
>
>On Tue, Feb 1, 2011 at 7:12 PM, Tommy Pham wrote:
>
>> > -Original Message-
>> > From: Brad Lorge [mailto:b...@lorge.com.au]
>> > Sent: Mo
; From: Brad Lorge [mailto:b...@lorge.com.au]
> > Sent: Monday, January 31, 2011 9:53 PM
> > To: php-general@lists.php.net
> > Subject: [PHP] Detecting Multi-Scope Variables
> >
> > Hello All,
> >
> > I am new to the list so please be gentle :)
> >
&
> -Original Message-
> From: Brad Lorge [mailto:b...@lorge.com.au]
> Sent: Monday, January 31, 2011 9:53 PM
> To: php-general@lists.php.net
> Subject: [PHP] Detecting Multi-Scope Variables
>
> Hello All,
>
> I am new to the list so please be gentle :)
>
>
Hello All,
I am new to the list so please be gentle :)
I am working on a PHP framework and have run up against a functionality
hurdle which I keep falling at. Basically, I have three mechanisms which all
function in a similar way and require this functionality: templating, event
handling and "act
6 matches
Mail list logo