headers
Kalle Sommer Nielsen | 1 Jul 2009 08:05
Picon
Gravatar

Re: [PHP-DEV] Re: Throwing E_DEPRECATED on startup

2009/6/30 Hannes Magnusson <hannes.magnusson <at> gmail.com>:
>
> Now that 5.3.0 is out, are you looking into fixing run-tests.php or all tests?

run-tests.php seems most reasonable to fix, and then those tests that
fail (aka. those who havnt been updated to catch these warnings).

>
> Like I warned about; if you enable any of these features in your
> php.ini and then run the test suite.. there are only a handful of
> tests that actually pass.

I can see us passing -n parameter to the binary when executing a test,
as most tests rely on the default builtin values in php.

-- 
regrads,

Kalle Sommer Nielsen
kalle <at> php.net

--

-- 
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
Permalink | Reply | 1 comment |
headers
Hannes Magnusson | 1 Jul 2009 09:32
Picon
Gravatar

Re: [PHP-DEV] Re: Throwing E_DEPRECATED on startup

On Wed, Jul 1, 2009 at 08:05, Kalle Sommer Nielsen<kalle <at> php.net> wrote:
> 2009/6/30 Hannes Magnusson <hannes.magnusson <at> gmail.com>:
>> Like I warned about; if you enable any of these features in your
>> php.ini and then run the test suite.. there are only a handful of
>> tests that actually pass.
>
> I can see us passing -n parameter to the binary when executing a test,
> as most tests rely on the default builtin values in php.

That defeats the point of the tests. They need to be tested under
various configurations.

For those tests that require special INI settings we have the --INI--
section to make sure those are set the way the test requires it.
Everything else should work under other configurations.

-Hannes

--

-- 
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
Permalink | Reply | 0 comments |
headers
Jani Taskinen | 1 Jul 2009 09:48
Picon
Gravatar

Re: [PHP-DEV] Re: Throwing E_DEPRECATED on startup

Uwe Schindler wrote:
> I had the same this morning when I compiled PHP on my solaris machine. The
> php.ini from my system-wide lib folder was used for the tests. In my case it
> claimed about the deprecated *_long_arrays setting (or something like that).
> Almost no test worked until I edited my global php.ini.
> 
> Tests should use a local php.ini in the build directory.

Well, actually they do use local ini. It's just sanitized version of 
your global one.

--Jani

--

-- 
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
Permalink | Reply | 0 comments |
headers
Greg Beaver | 1 Jul 2009 16:00
Favicon

[PHP-DEV] Re: php 5.3 on windows does not work with go-pear.phar

Christian Weiske wrote:
> Hi,
>
>
> Several users reported that the windows package of php 5.3 does not work with the phar:
> - http://pastebin.com/d79a424b3
> - http://pastebin.com/d49c8cc02
>
> phar "C:\Users\Sebastian Bergmann\php\PEAR\go-pear.phar" does not have a signature
> Warning: require_once(phar://go-pear.phar/index.php): failed to open stream: phar error: invalid
url or non-existent phar "phar://go-pear.phar/index.php" in C:\
> Users\Sebastian Bergmann\php\PEAR\go-pear.phar on line 1236

Sorry about this problem, the fix is simple, is not a bug in PHP or in
phar, and is just a developer oversight.

First, add "-drequire_hash=0" to go-pear.bat as a temporary fix for
those who already have PHP 5.3.0, and the permanent fix is to
re-generate the go-pear.phar on a machine with ext/phar installed.

I am not sure how this slipped through, perhaps I have the
require_hash=0 in my php.ini on windows and forgot about it (will have
to check)

Greg

--

-- 
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
(Continue reading)

Permalink | Reply | 4 comments |
headers
Sebastian Bergmann | 1 Jul 2009 16:28
Picon
Gravatar

Re: [PHP-DEV] Re: php 5.3 on windows does not work with go-pear.phar

Greg Beaver schrieb:
> First, add "-drequire_hash=0" to go-pear.bat as a temporary fix for
> those who already have PHP 5.3.0, and the permanent fix is to
> re-generate the go-pear.phar on a machine with ext/phar installed.

 That should have been "-d phar.require_hash=0", I guess.

-- 
Sebastian Bergmann                    Co-Founder and Principal Consultant
http://sebastian-bergmann.de/                           http://thePHP.cc/

--

-- 
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
Permalink | Reply | 2 comments |
headers
Greg Beaver | 1 Jul 2009 17:39
Favicon

Re: [PHP-DEV] Re: php 5.3 on windows does not work with go-pear.phar

Sebastian Bergmann wrote:
> Greg Beaver schrieb:
>> First, add "-drequire_hash=0" to go-pear.bat as a temporary fix for
>> those who already have PHP 5.3.0, and the permanent fix is to
>> re-generate the go-pear.phar on a machine with ext/phar installed.
> 
>  That should have been "-d phar.require_hash=0", I guess.

Hi,

This is correct, sorry again.

Greg

--

-- 
PEAR Development Mailing List (http://pear.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
Permalink | Reply | 0 comments |
headers
Carsten Wiedmann | 1 Jul 2009 18:39
Picon
Picon

[PHP-DEV] [5.3] Howto build mysql, mysqli and pdo_mysql with libmysql on Windows

Hi all,

anybody knows, how to build especially pdo_mysql with libmysql on Windows
(I've managed to build mysql and  mysqli with a change in the config.w32 files)?

My configure string is something like:
| cscript /nologo configure.js --disable-all \
|                              ... \
|                              --without-mysqlnd \
|                              --with-mysql=shared \
|                              --with-mysqli=shared \
|                              --with-pdo-mysql=shared

The build stops with errors in mysql_statement.c, like:
| mysql_statement.c(52) : error C2039: 'stmt'

mysql and mysqli are working fine. All three extensions are working and
build with mysqlnd.

However, how can I connect to a named pipe with mysqlnd. All my scripts are
using the usual hostname = ".". But that's not working with a mysqlnd build.

Another question:

With a default PHP 5.3 installation, I just changed:
| log_errors = On
| error_log = php_errors.log

(date.timezone is still not defined.) Now, if I do a "php -i" in the shell I
have this repeating message in a loop (and a lot of entries in the defined log):
(Continue reading)

Permalink | Reply | 0 comments |
headers
Ilia Alshanetsky | 1 Jul 2009 18:59

[PHP-DEV] RFC: Type hinting revisited for PHP 5.3

There has been quite a bit of discussion on this list, IRC, developer  
meetings, etc... about introduction of type hinting to PHP. Most  
people appear to think that this would be a good idea, but there is a  
reason why it is not in PHP already. The main source of conflict  
appears to be that in some cases typical type hinting is just too  
strict for PHP's typeless nature (most people expect that "1" == 1,  
while int type hint would definitely reject string "1").  Personally,  
I disagree with that opinion, but I can understand people who raise  
that issue. At work we've been using PHP 5.2 with type hinting for  
nearly 2 years now with great success, it makes code much easier to  
read and understand and the security benefit of type hinting is not to  
be under valued. In many cases type hinting can present a last line of  
defense against unexpected input for numeric fields, which are  
typically abused to do SQL injection.

I've taken a few hours this morning to port my 5.2 type hinting patch  
to 5.3. In recognition of a need for a more 'flexible' numeric type  
I've introduced (numeric) type hint that would allow bool/int/float  
data types as well as a string containing a numeric entity as  
identified by is_numeric_string(). For completion i've also added  
(scalar) data type that will allow any scalar data element.

The patch is available here: http://ia.gd/patch/type_hint_53.txt

It should be noted that this patch is fully compatible with opcode  
caches and and requires no changes on the part of an opcode cache such  
as APC to work.

My hope is that the latest changes will allow this to become a  
standard part of PHP.
(Continue reading)

Permalink | Reply | 58 comments |
headers
Gwynne Raskind | 1 Jul 2009 19:09

Re: [PHP-DEV] RFC: Type hinting revisited for PHP 5.3

On Jul 1, 2009, at 12:59 PM, Ilia Alshanetsky wrote:
> There has been quite a bit of discussion on this list, IRC,  
> developer meetings, etc... about introduction of type hinting to  
> PHP. Most people appear to think that this would be a good idea, but  
> there is a reason why it is not in PHP already. The main source of  
> conflict appears to be that in some cases typical type hinting is  
> just too strict for PHP's typeless nature (most people expect that  
> "1" == 1, while int type hint would definitely reject string "1").   
> Personally, I disagree with that opinion, but I can understand  
> people who raise that issue. At work we've been using PHP 5.2 with  
> type hinting for nearly 2 years now with great success, it makes  
> code much easier to read and understand and the security benefit of  
> type hinting is not to be under valued. In many cases type hinting  
> can present a last line of defense against unexpected input for  
> numeric fields, which are typically abused to do SQL injection.
[snip]
> My hope is that the latest changes will allow this to become a  
> standard part of PHP.

+1 (+1000, actually :)

-- Gwynne

--

-- 
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
Permalink | Reply | 1 comment |
headers
Alain Williams | 1 Jul 2009 19:15
Picon
Favicon

Re: [PHP-DEV] RFC: Type hinting revisited for PHP 5.3

On Wed, Jul 01, 2009 at 12:59:59PM -0400, Ilia Alshanetsky wrote:
> There has been quite a bit of discussion on this list, IRC, developer  
> meetings, etc... about introduction of type hinting to PHP. Most  
> people appear to think that this would be a good idea, but there is a  
> reason why it is not in PHP already. The main source of conflict  
> ...

Another desirable result of type hinting is that it would strengthen
reflection ... one use of that would be automatic generation of
WSDL files. This is something that I am currently struggling to do,
not helped by the completely cr*p documentation of this - I am not
talking about PHP documentation here by W3 & other places :-(

+1 to type hinting.

-- 
Alain Williams
Linux/GNU Consultant - Mail systems, Web sites, Networking, Programmer, IT Lecturer.
+44 (0) 787 668 0256  http://www.phcomp.co.uk/
Parliament Hill Computers Ltd. Registration Information: http://www.phcomp.co.uk/contact.php
Past chairman of UKUUG: http://www.ukuug.org/
#include <std_disclaimer.h>

--

-- 
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
Permalink | Reply | 5 comments |

Gmane