Zend API changes
| From: | Brian Foddy | Date: | Fri, 04 May 2001 15:29:26 +0000 |
| Subject: | Zend API changes | ||
| Groups: | php.dev | ||
| Request: | Send a blank email to php-dev+get-53859@lists.php.net to get a copy of this message | ||
A small point I'd like to raise here.
I noticed 4.0.5 made a change to the arguments of
zend_hash_get_current_key
by adding a "dupe" argument to the define and underlying function.
This of course broke any external custom modules that are not
changed appropriately. In this case the change was very simple,
but it raises a good question...
Are there some guidelines independent external modules can follow
to remain more compatible between releases? I'm not questioning
the right or need for underlying Zend API changes, obviously
when such changes are made all functions inside the PHP collection
are change accordingly. But are there suggestions to minimize
these in the future and get better notified when they do occur?
Thanks,
Brian