[PHP-DEV] Re: 5.2.5 - changes in the string parser

>> The documentation probably should be fixed. Also, \f and \v have been >> documented; your mirror probably isn't up to date. See: >> http://cvs.php.net/viewvc.cgi/phpdoc/en/language/types.xml?r1=1.189&r2=1.190&diff_format=u This is the mirror I'm using - http://www.php.net/manual/en/language.ty

[PHP-DEV] [PATCH] consting ext/standard/dl.c

Here's dl.c Is the Zend directory doable as well, or is that off-limits for some reason or another? That's really the place I should be working on first, because it's the lowest level. xoxo, Andy -- Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance Index: ext/standard/dl.c =

[PHP-DEV] [PATCH] Constifying ext/standard/md5.c

Here's some patchy goodness to constify the input args to the md5 functions. xoxo, Andy -- Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance Index: ext/standard/md5.c === --- ext/standard/md5.c (revision 1) +++

[PHP-DEV] Re: 5.2.5 - changes in the string parser

Dagdamor wrote: > I checked the documentation. It says that only "\n", "\r" and "\t" sequences > (I count only alphanumeric ones) are special, there is nothing about \f or \v. > The documentation clearly says that all other sequences are not special and > the backslash becomes part of the string. I

[PHP-DEV] Re: 5.2.5 - changes in the string parser

Dagdamor wrote: > I am reporting about the changes that were made in the string parser in 5.2.5. > From this version, sequences "\f" and "\v" are special and are parsed as FF > and VT symbols. See: http://bugs.php.net/bug.php?id=42590 In my opinion, if you have stray backslashes in double-quotes

[PHP-DEV] 5.2.5 - changes in the string parser

Hello. I am reporting about the changes that were made in the string parser in 5.2.5. >From this version, sequences "\f" and "\v" are special and are parsed as FF and VT symbols. IMHO that doesn't make sense because the behavior was different in the older versions of PHP, and will affect many exis

Re: [PHP-DEV] Re: Quick question before submitting a feature request...

Alexey Zakhlestin wrote: > In PHP all exceptions have "Exception" as a parent-class Indeed you are right! Even better. -- Edward Z. YangGnuPG: 0x869C48DA HTML Purifier Anti-XSS Filter [[ 3FA8 E9A9 7385 B691 A6FC B3CB A933 BE7D 869C 48DA ]] --

Re: [PHP-DEV] Re: Quick question before submitting a feature request...

On 11/23/07, Edward Z. Yang <[EMAIL PROTECTED]> wrote: > I understand this solution won't work if application > Exceptions don't have a common parent class, but this is already > recommended as a good practice. In PHP all exceptions have "Exception" as a parent-class -- Alexey Zakhlestin http://

[PHP-DEV] Re: Quick question before submitting a feature request...

Ken Stanley wrote: > The problem that I run into, that I feel could be improved, is that if the > view class throws the exception during exception handling, I get the error, > "Fatal error: Exception thrown without a stack frame in Unknown on line 0." This may be a documentation problem. set_excep

Re: [PHP-DEV] Quick question before submitting a feature request...

Anthony, thank you for your response. Would it not be possible that when an exception is thrown to temporarily store the filename/line number for when the exception handler kicks in, so at the very least, if someone made the mistake of throwing an exception inside of another exception, they could a

Re: [PHP-DEV] Quick question before submitting a feature request...

On 22.11.2007 06:12, Ken Stanley wrote: > I have > corrected my mistake so that it will use trigger_error() instead of throwing > an exception. However, in my Google searches I have noticed that there are a > lot of people having somewhat similar problems, but without an easy > solution. My feature

Re: [PHP-DEV] Quick question before submitting a feature request...

Ken, This same issue was referred to back in 2004 on the php.net site. I just looked it up and the post can be found by [EMAIL PROTECTED] from 9 September, 2004, on this page: http://us.php.net/errorfunc On Nov 23, 2007 12:32 AM, Ken Stanley <[EMAIL PROTECTED]> wrote: > I complet

Re: [PHP-DEV] Banning old versions

Hello Rasmus, right, so we only need to add the other two. marcus Friday, November 23, 2007, 5:44:11 PM, you wrote: > Marcus Boerger wrote: >> Hello internals, >> >> can we please officially announce the end of support for PHP 4*, 5.0.*, >> 5.1.* as 31st december 2007? Officially as in on

Re: [PHP-DEV] Banning old versions

Marcus Boerger wrote: > Hello internals, > > can we please officially announce the end of support for PHP 4*, 5.0.*, > 5.1.* as 31st december 2007? Officially as in on the front of php.net. We already set the EOL date for PHP 4. August 8, 2008. See the 4th entry down on the php.net front page

Re: [PHP-DEV] Banning old versions

I don't know about the "quite a while", but definitely for a few more months still. On 23-Nov-07, at 10:14 AM, Marcus Boerger wrote: Hello Ilia, ok, then who is going to write the entry for 4, 5.0 and 5.1? To me it sounds like a job for one of the active RMs (Derick, Ilia, Johannes). And

Re: [PHP-DEV] Banning old versions

Hello Ilia, ok, then who is going to write the entry for 4, 5.0 and 5.1? To me it sounds like a job for one of the active RMs (Derick, Ilia, Johannes). And I definitively agree, 5.2 will be around for quite a while. marcus Friday, November 23, 2007, 3:56:29 PM, you wrote: > I think 5.2 will b

Re: [PHP-DEV] Banning old versions

I think 5.2 will be alive for a while longer, at least until 5.3.X stable is released. 5.0 and 5.1 have long been dead, I think we can safely announce their EOL today if we wanted to. On 23-Nov-07, at 9:24 AM, Antony Dovgal wrote: On 23.11.2007 17:16, Marcus Boerger wrote: Hello internals

Re: [PHP-DEV] Banning old versions

On 23.11.2007 17:16, Marcus Boerger wrote: > Hello internals, > > can we please officially announce the end of support for PHP 4*, 5.0.*, > 5.1.* as 31st december 2007? Officially as in on the front of php.net. Yes, we're coming to the end of 5.2 branch soon, so it would make sense to make it

[PHP-DEV] Banning old versions

Hello internals, can we please officially announce the end of support for PHP 4*, 5.0.*, 5.1.* as 31st december 2007? Officially as in on the front of php.net. Best regards, Marcus -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php

RE: [PHP-DEV] late static binding php6

Hi Marcus, ahh now i know whats my thinking problem. :) the new introduced function get_called_class() function gives me the information how to work around my problem. :) static isnt really required. :) -- Marco > -Original Message- > From: Marcus Boerger [mailto:[EMAIL PROTECTED] > Sen

Re: [PHP-DEV] late static binding php6

Hello Richard, what's your point? The output of this script with updated checks and inheritence still gives expected results: If you wanted to prevent further inheritance you'd simply mark the class as final. Say 'final class bar' would prevent existance of 'baz'. I wonder if we shouldn't make

Re: [PHP-DEV] late static binding php6

On 23/11/2007, Marcus Boerger <[EMAIL PROTECTED]> wrote: > Hello Richard, > > that kind of stuff is the reason we added LSB. There is only one tiny > thing I am not to happy about. You do not at all have to declare static > $instance. Simply because you never use it. And for that reason you guys

Re: [PHP-DEV] late static binding php6

Hello Richard, that kind of stuff is the reason we added LSB. There is only one tiny thing I am not to happy about. You do not at all have to declare static $instance. Simply because you never use it. And for that reason you guys have your code worng. Use the following snippet for verification:

Re: [PHP-DEV] Cleanup and maintenance of internal C code

Hello Andy, changing to const where possible is a damn good thing and on our list for long. We also wanted to get rid of TSRMLS_FETCH() wherever possible. For instance we should do this change: typedef int (*apply_func_args_t)(void *pDest, int num_args, va_list args, zend_hash_key *hash_key); Z

RE: [PHP-DEV] late static binding php6

Hi Richard, the problem is this: NEW INSTANCE object(foo)#1 (0) { } NEW INSTANCE object(bar)#2 (0) { } object(foo)#1 (0) { } object(bar)#2 (0) { } This means i just called once the constructor for the singleton abstract for every main class (foo, bar) But if you remove the static member $_ins

Re: [PHP-DEV] late static binding php6

On 23/11/2007, Richard Quadling <[EMAIL PROTECTED]> wrote: > On 22/11/2007, Marco Kaiser <[EMAIL PROTECTED]> wrote: > > Hi again, > > > > to explain the main idea a bit more, the code below work and moves the > > main getInstance function from the class and its possible to abstract > > this. > > it

Re: [PHP-DEV] late static binding php6

On 22/11/2007, Marco Kaiser <[EMAIL PROTECTED]> wrote: > Hi again, > > to explain the main idea a bit more, the code below work and moves the > main getInstance function from the class and its possible to abstract > this. > it would be cool to get the protected property also into the abstract > cla