Hi Richard, I've heard of a lot of people with little scripts running around, that need *really need* magic quotes enabled. (j/k) All joking aside I know that probably having something running fine for 8+ years is great. Congrats on that achievement!
There are reasons to evolve things to the point where older code really can't remain compatible - obvious disclaimer: I don't use ext/imap I'm biased when it doesn't hurt me... - but I think that security or lack of maintenance might be the two crucial points that might culminate in that decision when thinking long term. That's not to say you shouldn't voice your opinions, specially when you're dependant on the ext, be it for a larger project, or for a personal geeky filter I congratulated you on earlier. But if the ext is no longer being maintained, even if working properly for the time being, there might be a point to marking it deprecated, with proper directions for alternatives/migrations. The problem is not today, or these past 8+ years it's been working wonderfully for you; but what happens when you're keeping the ext active [i.e. not deprecated], and problems come around some time from now. Since it's unmaintained, there might be a problem when there's no one wanting to fix it... You should probably find confort in also having a better code with a more robust API, even though you might be forced into touching something you havent for 8+ years (we all know how that feels like). If not, then at least consider this should be marked as deprecated (even without a due date for complete removal), just for the sake of no longer being maintained! ~ Daniel Macedo -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
