OK, has anyone enough time to commit this please?
I left the extension API change out of it though (the ME_* support) - does
that really need to go in there too?
----- Original Message -----
From: "Pierre" <[EMAIL PROTECTED]>
To: "Steph Fox" <[EMAIL PROTECTED]>
Cc: "Michael B Allen" <[EMAIL PROTECTED]>; <internals@lists.php.net>
Sent: Thursday, September 14, 2006 7:39 PM
Subject: Re: [PHP-DEV] Module API Changes
Hello,
On 9/14/06, Steph Fox <[EMAIL PROTECTED]> wrote:
Hi Michael, Pierre -
Erm, no they aren't in the upgrade guide, because the upgrade guide is
aimed
at user issues and this was seen primarily as an extension author issue.
Do
people generally think the module and extension API bumps should be in
there?
Rasmus was talking about the internals change and ask if they can be
put in this file. I think it is a very good suggestion and no, I did
not have the time (and will not in the next 10 days) to do it :)
--Pierre
Index: README.UPDATE_5_2
===================================================================
RCS file: /repository/php-src/Attic/README.UPDATE_5_2,v
retrieving revision 1.1.2.15
diff -u -r1.1.2.15 README.UPDATE_5_2
--- README.UPDATE_5_2 11 Sep 2006 23:11:18 -0000 1.1.2.15
+++ README.UPDATE_5_2 14 Sep 2006 17:57:18 -0000
@@ -25,6 +25,23 @@
under PHP CLI. All methods map to existing procedural date functions.
+========================
+Module API number change
+========================
+
+Following a series of issues surrounding the loading and unloading of PHP
+extensions, an entirely new - and infinitely more stable - module API was
+introduced in PHP 5.2. This means that PHP 5.2 will abort the process when
+attempting to load an extension built against a version of PHP 5 pre-dating
+the change made on 19th May 2006. Extension authors should be aware that the
+internal code itself has retained back compatibility. Simply building your
+extension against PHP 5.2 will solve the loading problem, although it will
+also leave your extension open to the same issues that prompted the change
+in the first place.
+
+Note: This does not in any way affect the status of the dl() function, which
+is still marked as deprecated.
+
==================================
Items from the NEWS file explained
==================================
@@ -127,7 +144,7 @@
Please refer to the PHP Manual for details.
-- Improved memory manager and increased default memory limit (Dmitry)
+- Improved memory manager and increased default memory limit. (Dmitry)
The new memory manager allocates less memory and works faster than the
previous incarnation. It allocates memory from the system in large blocks,
@@ -138,17 +155,17 @@
all the memory overhead used by the malloc library.
Thanks to this new-found accuracy memory usage may appear to have increased,
- although actually it has not. To accommodate this apparent increase, the
+ although actually it has not. To accommodate the apparent increase, the
default memory_limit setting was also increased - from 8 to 16 megabytes.
-- Changed priority of PHPRC environment variable on win32 (Dmitry)
+- Changed priority of PHPRC environment variable on win32. (Dmitry)
The PHPRC environment variable now takes priority over the path stored
in the Windows registry.
-- Added notice when accessing return value from __get() in write mode (Marcus)
+- Added notice when accessing return value from __get() in write mode. (Marcus)
The reason for this is that __get() only returns variables in read mode, and
it is therefore not possible to write to the returned variable. In previous
@@ -161,10 +178,10 @@
cast the returned value from __get() to an array, or use SPL's ArrayObject
instead of an array.
-- CLI SAPI no longer checks cwd for php.ini or the php-cli.ini file (Edin)
+- CLI SAPI no longer checks cwd for php.ini or the php-cli.ini file. (Edin)
- In PHP 5.1.X an undocumented feature was added that made the CLI binary
- check the current directory for PHP configuration file possibly leading to
- unpredictable behavior due to an un-expected configuration file being
- read. This functionality was removed in 5.2 and PHP will no longer search
- CWD for the presence of the php.ini or the php-cli.ini files.
+ In PHP 5.1.X an undocumented feature was added that made the CLI binary
search
+ the current directory for the PHP configuration file, potentially leading to
+ unpredictable behavior due to an unexpected configuration file being read.
+ This functionality was removed in 5.2, and PHP CLI will no longer check CWD
+ for the presence of a php.ini or php-cli.ini file.
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
