Hi Jani,
Its all set. I've got back and fixed the problems I was getting while
compiling, so there are now no existing lines of code commented out. There
are several that were removed, all having something to do with
SWFMovie_output, for example:
#ifdef HAVE_NEW_MING
We can left that out. The flag to search in the include path is available
to all file_* functions in PHP. Make it sense to search in the include path
for example in the exif-functions? But this parameter is available there,
too. So for consistency I added this parameter.
At 16:37 15.04.2005,
Uwe Schindler wrote:
We can left that out. The flag to search in the include path is
available to all file_* functions in PHP. Make it sense to search in the
include path for example in the exif-functions? But this parameter is
available there, too. So for consistency I added this parameter.
I can remove this parameter. Without it, the function declaration keeps
constant and we could add this patch to PHP_5_0, too. It does not change
the user interface but makes C code simplier and adds support for URLs
without any cost to it.
The original intention to change the md5/sha1 code was
On Fri, 15 Apr 2005, Uwe Schindler wrote:
I can remove this parameter. Without it, the function declaration keeps
constant and we could add this patch to PHP_5_0, too. It does not change the
user interface but makes C code simplier and adds support for URLs without any
cost to it.
I think
On Fri, 15 Apr 2005, Andrey Hristov wrote:
Uwe Schindler wrote:
We can left that out. The flag to search in the include path is available to
all file_* functions in PHP. Make it sense to search in the include path for
example in the exif-functions? But this parameter is available there,
Jani, Albert, have I missed something? I don't see what this has to do with my
update, is this a mistake or am I missing something?
Thanks,
-
Birdstep Technology John Higgins
Office: 206 748 5353
We can left that out. The flag to search in the include path is
available to
all file_* functions in PHP. Make it sense to search in the include
path for
example in the exif-functions? But this parameter is available there,
too.
So for consistency I added this parameter.
Except that
Maintaining compatibility between different major versions of PHP must
be extremely hard. Maybe that is obvious, but I do not quite understand
why developers do it. Why PHP 5 has to understand deprecated syntax of
PHP 4? I mean, if someone needs to execute old scripts, they can always
use old
At 18:51 15.04.2005, Sara Golemon wrote:
Rather than getting prototype change happy. How about a context parameter
for the file:// wrapper since it only applies to plainfiles anyway. (Note:
Okay so it applies to plainfile wrappers like compress.gzip:// but that just
opens the subordinate
The advantage of maintaining reverse compatibility is that it helps encourage
people to upgrade. Many more people would have many more concerns if the
4 - 5 upgrade broke programs using depreciated practices. ISPs and hosting
companies in particular would be extremely reluctant to upgrade as it
Parameter removed again. Any complaints to add this patch (lowlevel file
io to streams in sha1_file md5_file) to PHP_5_0 (PHP_4_3 ???), too?
I have no objections to MFHing the path to 4.3.
Ilia
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit:
Hello!
Can someone tell me anything about the state of PHP5 support in APC? I
have read some posts from last september where was statet in a few
weeks there will be PHP5 support ;-)
Today I tried to install a snapshot from CVS, to see if it works with
PHP 5.0.3 on my Gentoo-Box. Seems if the
I'm sorry, should have gone to pecl.dev!
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
14 matches
Mail list logo
