Re: zend module patch - (aka versioning proposal?)

On Wed, 10 Oct 2001, Stig S. Bakken wrote: > > The patch also adds a "version" field to the struct, along with a > > zend_get_module_version Zend API function and an optional parameter to > > phpversion() for getting the version of a loaded extension. > > > > The downside is that moving zend_module_entry's configuration fields > > first can't be done in a backwards-compatible way. This patch breaks > > every extension out there (except ext/standard, which is updated), but > > it does buy us better BC possibilities in the future. > > > > Comments, opinions? Yes, I have one question about your proposed change. My C programming is very rusty, but I can see that you are treating the version information as a plain string (maybe I'm wrong). If this is true, how would we check against a minor version of an extension, as to be able to detect a specific version that might have a yet another very specific bugfix / feature ? I remember from a few weeks ago Andy talking about maybe creating a new function that would return the major version number and also the minor and micro numbers. All of that would be very helpful to create portable code that could check the available features that it needs. I would ask Jani to step on this discussion that moved from just a API breakage change to a Versioning scheme proposal. :) We definetly need more information than just a string containing the version of an extension. Cheers, Joao -- João Prado Maia <jpm@phpbrasil.com> http://phpbrasil.com - php com um jeitinho brasileiro -- Precisando de consultoria em desenvolvimento para a Internet ? Impleo.net - http://impleo.net/?lang=br