Re: Re: suggestion for pecl packages

> > I'm bundling up a runkit extension as we speak, I can throw in a > > runkit_ext_version() function while I'm at it (which will allow access to > > the version ID of other extensions too). Since my goal for the extension as > > a whole is compatability back to 4.0.0 this should cover your need. > > > I think that full compatibility back to 4.0.0 will be kind of impossible or? :) > Many extensions has this > #if ZEND_MODULE_API_NO >= 20010901 > "0.1", /* Replace with version number for your extension */ > #endif > The ZEND_MODULE_API_NO is after the release of 4.0.0 thus not every module > will give you back this info. And unfortunately in most cases devs usually > don't change this version :/ > That's true, I actually meant that the extension should be able to compile. Some functions may or may not be available depending on what's exposed/available within the API. I'm expecting the guy asking for the feature to be okay, even debian users are up to 4.1.2 by now. As to developers not changing that version (and I know I'm also guilty of that)... well... .whatcha gonna do? At least now that the ReflectionAPI exposes this value they can start being pestered with bugreports :) -Sara