RE: FW: [PHP-DEV] Long awaited line directive

2006-08-10 Thread Andi Gutmans
Some feedback from Stas on the subject. I agree with him completely but wanted to get a second opinion. Honestly I think while this is somewhat useful for auto-generated files, it's not worth the risk and effort. It's a very marginal feature and very few people will use it. Supporting it in a non-i

[PHP-DEV] PHP 5.1.5RC1 Released

2006-08-10 Thread Ilia Alshanetsky
The first and hopefully the last release candidate of PHP 5.1.5 is out and can be downloaded from here: http://downloads.php.net/ilia/php-5.1.5RC1.tar.bz2 6e120d88e366c895ed324089deefa755 http://downloads.php.net/ilia/php-5.1.5RC1.tar.gz 159525e68b9aff188ab84feef918eb5a This release is intende

Re: [PHP-DEV] libxml2/threading/win 2003

2006-08-10 Thread Rob Richards
Doesn't really matter where it is. The only reason I added it in libxml.c was since libxml2 was the first/only lib needing a DllMain in teh php5ts_xxx.dll build, I put it there so there was minimal changes to the core code. Evenutally I thought it might make more sense to me moved elsewhere so

[PHP-DEV] CVS Account Request: bobolsen

2006-08-10 Thread Bob Olsen
I would also like to maintain the PHP manual -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php

Re: [PHP-DEV] libxml2/threading/win 2003

2006-08-10 Thread Edin Kadribasic
Hi Rob, Since we're adding a DllMain function, shouldn't it be located in main/main.c. We might need to hook up other thread initialization stuff in there in the future. Edin Rob Richards wrote: In order to resolve reported crashing on win 2003, I have had to change the static libxml build

[PHP-DEV] Re: CVS Account Request: mahono

2006-08-10 Thread Lukas Kahwe Smith
Matthias Nothhaft wrote: I would like to commit changes to the LiveUser and LiveUser_Admin packages. Lukas told me to ask for cvs access. Thanks. Aye, he has my blessings :) regards, Lukas -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsu

Re: [PHP-DEV] Fatal errors

2006-08-10 Thread Michael Walter
What do you mean? Regards, Michael On 8/10/06, Marcus Boerger <[EMAIL PROTECTED]> wrote: Hello Michael, hwat are you doing there? You turn any new oop feature as oh php 5 into a joke. What do you aim at? Thursday, August 10, 2006, 12:02:09 PM, you wrote: > Hi, > right now, PHP triggers

[PHP-DEV] libxml2/threading/win 2003

2006-08-10 Thread Rob Richards
In order to resolve reported crashing on win 2003, I have had to change the static libxml builds to use the flag LIBXML_STATIC_FOR_DLL. This now requires a DllMain to be added within any dll that is building libxml2 in statically. PHP 4.x - domxml (use php_domxml.c.diff.txt patch) PHP 5.x/HEAD

Re: [PHP-DEV] ext/msql move to PECL

2006-08-10 Thread Edin Kadribasic
Hi, msql was obsolete back in 1999 when I was still using it. I doubt many people have touched it in this century, I don't think you need to move it to PECL. I think it should just be cvs deleted, and a note added that as of 5.2.0 we no longer support msql. Edin Antony Dovgal wrote: Hi a

Re: [PHP-DEV] ext/msql move to PECL

2006-08-10 Thread Edin Kadribasic
Antony Dovgal wrote: On 11.08.2006 00:33, Edin Kadribasic wrote: Hi, msql was obsolete back in 1999 when I was still using it. I doubt many people have touched it in this century, I don't think you need to move it to PECL. I think it should just be cvs deleted, and a note added that as of

Re: [PHP-DEV] ext/msql move to PECL

2006-08-10 Thread Antony Dovgal
On 11.08.2006 00:33, Edin Kadribasic wrote: Hi, msql was obsolete back in 1999 when I was still using it. I doubt many people have touched it in this century, I don't think you need to move it to PECL. I think it should just be cvs deleted, and a note added that as of 5.2.0 we no longer supp

[PHP-DEV] ext/msql move to PECL

2006-08-10 Thread Antony Dovgal
Hi all. I'd like to move ext/msql (Msql, not MSsql) to PECL before 5.2.0RC2 and curious how many of you have heard of people still using this extension. Personally I haven't heard of any. Anyone? -- Wbr, Antony Dovgal -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, vi

Re: [PHP-DEV] Fatal errors

2006-08-10 Thread Marcus Boerger
Hello Michael, this is the expected behavior. But we migth as well simply remove all those modifiers. That would be much better then providing them in a senseless manner. regards marcus Thursday, August 10, 2006, 12:02:09 PM, you wrote: > Hi, > right now, PHP triggers fatal errors e.g. when

[PHP-DEV] CVS Account Request: mahono

2006-08-10 Thread Matthias Nothhaft
I would like to commit changes to the LiveUser and LiveUser_Admin packages. Lukas told me to ask for cvs access. Thanks. -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php

Re: [PHP-DEV] Fatal errors

2006-08-10 Thread Pierre
Hello, On 8/10/06, Derick Rethans <[EMAIL PROTECTED]> wrote: On Thu, 10 Aug 2006, Ilia Alshanetsky wrote: > > On 10-Aug-06, at 9:35 AM, Michael Walter wrote: > > > What do you feel is incorrect about allowing mentioned errors to be > > handled in userspace? > > My feeling is that errors such as

Re: [PHP-DEV] Fatal errors

2006-08-10 Thread Derick Rethans
On Thu, 10 Aug 2006, Ilia Alshanetsky wrote: > > On 10-Aug-06, at 9:35 AM, Michael Walter wrote: > > > What do you feel is incorrect about allowing mentioned errors to be > > handled in userspace? > > My feeling is that errors such as visibility violations should be addressed > during debugging

Re: [PHP-DEV] Fatal errors

2006-08-10 Thread Unknown W. Brackets
In the past, many softwares have used an error handler function to provide the following cases: 1. Log the error in a more complicated way than PHP does by default. 2. Send off an email, if necessary, or communicate with another service. 3. Show a generic (e.g. a 500) error message to the client

Re: [PHP-DEV] HTTP-Only Patch

2006-08-10 Thread Ilia Alshanetsky
Scott, Thanks for the patch, it is now part of the 5.2 tree. Ilia -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php

Re: [PHP-DEV] Fatal errors

2006-08-10 Thread Ilia Alshanetsky
On 10-Aug-06, at 6:02 AM, Michael Walter wrote: Hi, right now, PHP triggers fatal errors e.g. when accessing private members or calling nonexistant functions. Since this is problematic for obvious reasons, what technical reasons are there for that behavior, and is there a chance that this beha

Re: [PHP-DEV] Fatal errors

2006-08-10 Thread Ilia Alshanetsky
On 10-Aug-06, at 9:35 AM, Michael Walter wrote: What do you feel is incorrect about allowing mentioned errors to be handled in userspace? My feeling is that errors such as visibility violations should be addressed during debugging and Q&A phase where simple error logging will be sufficien

Re: [PHP-DEV] Fatal errors

2006-08-10 Thread Michael Walter
What do you feel is incorrect about allowing mentioned errors to be handled in userspace? Regards, Michael On 8/10/06, Ilia Alshanetsky <[EMAIL PROTECTED]> wrote: On 10-Aug-06, at 6:02 AM, Michael Walter wrote: > Hi, > > right now, PHP triggers fatal errors e.g. when accessing private > membe

Re: [PHP-DEV] Re: Fatal errors

2006-08-10 Thread Michael Walter
Hi, On 8/10/06, Derick Rethans <[EMAIL PROTECTED]> wrote: He wasn't talking about *undefined variables* at all. The variable *is* defined as private and calling that is ofcourse not allowed. I was talking about all kinds of errors which for no good reason are non-recoverable. Surely, the opera

Re: [PHP-DEV] Re: Fatal errors

2006-08-10 Thread Pierre
Hello, On 8/10/06, Derick Rethans <[EMAIL PROTECTED]> wrote: On Thu, 10 Aug 2006, Pierre wrote: > On 8/10/06, Michael Walter <[EMAIL PROTECTED]> wrote: > > Yeah. It is problematic that the application has no chance of dealing > > with the errors itself (consider e.g. php-shell which has to go g

Re: [PHP-DEV] Re: Fatal errors

2006-08-10 Thread Derick Rethans
On Thu, 10 Aug 2006, Pierre wrote: > On 8/10/06, Michael Walter <[EMAIL PROTECTED]> wrote: > > Yeah. It is problematic that the application has no chance of dealing > > with the errors itself (consider e.g. php-shell which has to go great > > lengths to prevent fatal errors from user code leading

Re: [PHP-DEV] Re: Fatal errors

2006-08-10 Thread Michael Walter
That doesn't justify the error being non-recoverable, though. Regards, Michael On 8/10/06, Lukas Kahwe Smith <[EMAIL PROTECTED]> wrote: Pierre wrote: > Hello, > > On 8/10/06, Michael Walter <[EMAIL PROTECTED]> wrote: >> Yeah. It is problematic that the application has no chance of dealing >> w

Re: [PHP-DEV] Re: Fatal errors

2006-08-10 Thread Lukas Kahwe Smith
Pierre wrote: Hello, On 8/10/06, Michael Walter <[EMAIL PROTECTED]> wrote: Yeah. It is problematic that the application has no chance of dealing with the errors itself (consider e.g. php-shell which has to go great lengths to prevent fatal errors from user code leading to php-shell's terminati

Re: [PHP-DEV] Re: Fatal errors

2006-08-10 Thread Pierre
Hello, On 8/10/06, Michael Walter <[EMAIL PROTECTED]> wrote: Yeah. It is problematic that the application has no chance of dealing with the errors itself (consider e.g. php-shell which has to go great lengths to prevent fatal errors from user code leading to php-shell's termination, and still fa

[PHP-DEV] Re: Fatal errors

2006-08-10 Thread Michael Walter
Yeah. It is problematic that the application has no chance of dealing with the errors itself (consider e.g. php-shell which has to go great lengths to prevent fatal errors from user code leading to php-shell's termination, and still fails at doing this in the general case). Regards, Michael On 8

[PHP-DEV] Re: Fatal errors

2006-08-10 Thread Lukas Kahwe Smith
Michael Walter wrote: Hi, right now, PHP triggers fatal errors e.g. when accessing private members or calling nonexistant functions. Since this is problematic for obvious reasons, what technical reasons are there for that behavior, and is there a chance that this behaviour will change in a futu

Re: [PHP-DEV] PDO statement execute enhancement

2006-08-10 Thread Marian Kostadinov
This code here http://lxr.php.net/source/php-src/ext/pdo/pdo_stmt.c#301 is maybe the point where a solution can be provided checking for param ->paramno == -1 is enough to detect an incorrect parameter and silently ignore it or emit a notice. 2006/8/9, Luk

[PHP-DEV] Fatal errors

2006-08-10 Thread Michael Walter
Hi, right now, PHP triggers fatal errors e.g. when accessing private members or calling nonexistant functions. Since this is problematic for obvious reasons, what technical reasons are there for that behavior, and is there a chance that this behaviour will change in a future release? Regards, Mi

[PHP-DEV] [PATCH] *printf additions (#, g, G), updates, etc.

2006-08-10 Thread Matt W
Hi all, Here are patches to add the things to *printf() I asked about a few weeks ago. If people can look over it, test it more, commit it, whatever, that'd be great. :-) Sorry for the long message, but want to cover everything. *) Precision now works for integer type specifiers (inc. x/o/b), m