>> If you want to maintain compatibility to 4.0.6, do it someplace >> else. Anything in PHP cvs should be compatible with the latest CVS. >> Or move your extension elsewhere.
I appreciate your position, but the source checked in *IS* compatible with the latest version of PHP and uses the latest APIs. The only difference is that rather than delete backward compatibility, #ifdef constructs are used to choose. We have been down this road before. There is a reasonable expectation that extensions may differ subtly from extension to extension. I see no need to fork my source for 4.0.x and 4.1.x compatibility when it is simple enough to do with macros and maintain one source file. What is the problem guys? IMHO It is completely unprofessional to remove backward compatibility when it is not an absolute requirement. I have been coding for over 25 years, professionally for 20, so I think I have some experience at this. Am I the only one that thinks that this is important, or at least my right to assert as author of the extension? -- PHP Development Mailing List <http://www.php.net/> To unsubscribe, visit: http://www.php.net/unsub.php
