Re: mail() into separate extension?
| From: | George Schlossnagle | Date: | Mon, 18 Jul 2005 14:35:22 +0000 |
| Subject: | Re: mail() into separate extension? | ||
| References: | 1 2 3 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-17317@lists.php.net to get a copy of this message | ||
On Jul 18, 2005, at 10:30 AM, Andrew Yochum wrote:
On Jul 18, 2005, at 10:15 AM, George Schlossnagle wrote:Sure. They inevitably will have differing behaviors (if not, why not just have a single unified function). Given that, you'll have different behaviors on different machines in a way that is not terribly transparent to end-users. That's evil. Not that there's anything wrong with being evil from time to time. That's the reason that apd had a replace_function call for mucking with the symbol table. But that's something that should be done locally. GeorgeDrop-in replacements are evil. If you want to do this, you should just create a new function that does what you need to do and name it differently. If you're dead-set on doing a name-based replacement, then you should have your extension modify the symbol table directly, but again, this is evil. GeorgeGeorge, Can you please substantiate your statement that drop-in replacements are evil? I could only see them being a problem if they don't fully implement the existing API.