[prev in list] [next in list] [prev in thread] [next in thread] 

List:       zend-engine2
Subject:    Re: [Zend Engine 2] Redeclare functions and classes during  runtime
From:       "Jason Greene" <usrgre-php () tds ! net>
Date:       2001-10-11 17:03:21
[Download RAW message or body]

Are you suggesting overriding as in the OO style of overriding functions?
In that case would you be able to call the original function?
(That sounds like that would be a mess for the engine to track)

-Jason
----- Original Message ----- 
From: "Zeev Suraski" <zeev@zend.com>
To: "RADI Harald" <harald.radi@nme.at>
Cc: "'Mark Rogers'" <mark@quarella.co.uk>; <engine2@lists.zend.com>
Sent: Thursday, October 11, 2001 7:46 AM
Subject: RE: [Zend Engine 2] Redeclare functions and classes during runtime


> I don't like mutable {}, for the reason that it's very non intuitive.  Non 
> intuitive enough so that I don't know exactly what it means.
> 
> If we go for allowing explicit function redeclarations (not sure how I feel 
> about this yet) - it should be *very* clear:
> 
> override function foo()
> {
> }
> 
> or something along these lines.
> 
> Zeev
> 
> At 14:02 11-10-01, RADI Harald wrote:
> > > > How can it happend to redefine a function by accident?
> > >
> > > include('some.big.file.of.useful.functions');
> > > // ... later, probably inside
> > > // another included script...
> > > include('some.big.file.of.useful.functions');
> > >
> > > Silly, I know, but I see it all the time. (It's amazing how
> > > many people don't use include_once for a start, but we can't
> > > all be perfect :-)
> >
> >that's why i suggested the mutable { .. } block. then you simply can't
> >redefine
> >a function by accident and if, it wouldn't influence the global
> >namespace.
> >
> >harald.
> 


[prev in list] [next in list] [prev in thread] [next in thread]