Re: [RFC] build IDs proposal

> I meant "readable" :) > >> Do you mean this? >> fprintf(stderr, "%s requires Zend Engine API version %d.\n" >> "The Zend Engine API version %d which is installed, is >> outdated.\n\n", >> new_extension->name, >> First of all, php error_log may not get this message because it's thrown >> into stderr. > > It is not possible at this stage. It is possible at this stage. Just put zend_error() call and you'll see it works and calls regular php error handler. And for example ioncube (it is a known zend extension) uses this "feature". > > >> What's about server admins who will be installing the extensions? > > An admin should know that, really. I don't see any reason why would all admins learn this core "feature" of php? Why not just make it providing clearer error messages? Such error message like "BogusName requires Blah blah blah Engine Api version XYXYXYX, and Blah blah blah Engine Api version YXYXYXYX is installed, is outdated" is just insane. By seeing these two numbers XYXYXYX and YXYXYXYX, whould anybody non-involved in core php development guess that this relates to php versions? Does that "BogusName" tell anything about real module name that caused the error, despite the fact that error itself in some cases is just not visible. -jv