Runkit / Parsekit & good practices
| From: | 131 | Date: | Sat, 20 Oct 2007 21:06:23 +0000 |
| Subject: | Runkit / Parsekit & good practices | ||
| Groups: | php.general | ||
| Request: | Send a blank email to php-general+get-263452@lists.php.net to get a copy of this message | ||
I was asking myself if the super-possibilities offered by the runkit
extension could be used in a "good" way
I'll like to use runkit to define superglobals like $config, for example./
I'll like to use runkit to modify Class extension & implementation, making
it more "Javascript" like.
I'm very frustated in not beeing able to extend an existing classes
For example, i'll like to use, in every one of my script "sql" static
classe, regardless the database system. - i know about PDO, that's just an
example -
I'll like to use
class sql {
//noting here
}
And in mysql.php
modify sql {
function connect(){
}
}
and in mysql/plugin/superlinks
modify sql {
function fetch(){
$tmp=before:fetch();
return $tmp=str_replace("<a href=....","<a href='FOO',..);
}
}
That's not a great post, my true question is
"Might we use the supergodpower runkit offers", or - not
PS : that's just an evolution of the EXISTING "Overload" process