Re: [PHP-DEV] Reference handling change and PHP 4.4.0

Hi I was lost in this thread. Could someone post resume from this discussion? How can I deal with this in 4.3, 4.4, 5+? Thanks -- Ondrej Ivanič ([EMAIL PROTECTED]) -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php

Re: [PHP-DEV] Reference handling change and PHP 4.4.0

Pierre Joye wrote: All the points I tried to explain in the last 2 months or so were about that and only that. Every oppinions have been raised. Short versions: Stop pollitic :) Pierre I think *ONE* problem here was that those of us who have moved on from PHP4 were probably not taking any

[PHP-DEV] quite a big bug in DOM

Hi, I found a bug in DOM. It surprises me that it's never been seen and/or fixed before. I can't find anything about in the PHP bugtracker anyway. The reason why I'm posting here and not writing a bugreport, is because I'm not sure if this is a problem in the PHP-extension or the DOM-library itsel

[PHP-DEV] Re: quite a big bug in DOM

To make it extra clear, what is outputted where the   is are 2 bytes: ascii codes 194 and 160. The 160 is the spacing character that is expected, but the 194 (the letter A with a ^ on top) is pretty magical and annoying. Some other (but not all) HTML-characters (e.g. ë) seem to have the same probl

Re: [PHP-DEV] quite a big bug in DOM

On Fri, Sep 16, 2005 at 10:06:40AM +0200, Ron Korving wrote: > Hi, > > I found a bug in DOM. It surprises me that it's never been seen and/or fixed > before. I can't find anything about in the PHP bugtracker anyway. The reason > why I'm posting here and not writing a bugreport, is because I'm not

Re: [PHP-DEV] quite a big bug in DOM

Damn.. I feel stupid now... Sorry guys. Is it normal for DOM to output everything in UTF8 without an ability to influence this? I figured that it wouldn't be a UTF8 problem because it outputs 2 bytes, and I thought UTF8 was just 1 byte (hence the name UTF8). Guess I was wrong. Sorry again, I reall

Re: [PHP-DEV] quite a big bug in DOM

""messju mohr"" <[EMAIL PROTECTED]> schreef in bericht news:[EMAIL PROTECTED] A thank you to you as well. In general: By the way, wouldn't it be time for trim() to start trimming off ascii characters 160 too since that's what   represents? It's no biggy, but maybe something to consider. Ron --

Re: [PHP-DEV] quite a big bug in DOM

On 16.9.2005 10:06 Uhr, Ron Korving wrote: > Hi, > > I found a bug in DOM. It surprises me that it's never been seen and/or fixed > before. I can't find anything about in the PHP bugtracker anyway. The reason > why I'm posting here and not writing a bugreport, is because I'm not sure if > this i

Re: [PHP-DEV] PATCH for #34505 (was 5.1.0RC2)

Just commit. On Thu, 15 Sep 2005, Antony Dovgal wrote: On 15.09.2005 03:24, Antony Dovgal wrote: On 14.09.2005 15:20, Zeev Suraski wrote: Any last minute additions to 5.1.0RC2 or can we roll it? If it's not too late I'd like to fix http://bugs.php.net/bug.php?id=34505 before RC2. It

Re: [PHP-DEV] PATCH for typo in zend_compile.c (was 5.1.0RC2)

Just commit (tm). On Thu, 15 Sep 2005, Antony Dovgal wrote: On 14.09.2005 15:20, Zeev Suraski wrote: Any last minute additions to 5.1.0RC2 or can we roll it? It seems that #27145 has crept back into 5.1 with a copy/paste typo. Here is the patch for it too. -- Donate @

Re: [PHP-DEV] PHP6, Unicode for language functions, classes,methods, vars names

On Fri, 16 Sep 2005, Pierre Joye wrote: On 9/16/05, Andi Gutmans <[EMAIL PROTECTED]> wrote: Jani, I don't really see how PHP 6 can support a build without ICU. With the whole core using the ICU library it's almost like not supporting libC. If you find a way I'd be happy to hear about it and di

[PHP-DEV] HEAD == PHP 7 (Was: Re: [PHP-DEV] PHP6, Unicode for language functions, classes,methods, vars names)

On Thu, 15 Sep 2005, Andi Gutmans wrote: I don't really see how PHP 6 can support a build without ICU. With the whole Call that version PHP 7. core using the ICU library it's almost like not supporting libC. If you find a way I'd be happy to hear about it and discuss but I think it's not

Re: [PHP-DEV] PHP6, Unicode for language functions, classes,methods, vars names

On 9/16/05, Jani Taskinen <[EMAIL PROTECTED]> wrote: > I really meant what I said. Like Andi said, PHP 6 won't > be out very soon, but I'd really like to have the cleaned > up PHP, preferrably yesterday. This year is fine too. > > And without unicode.. Having a PHP6 and a PHP

Re: [PHP-DEV] quite a big bug in DOM

On Fri, 16 Sep 2005, Ron Korving wrote: > Damn.. I feel stupid now... Sorry guys. > Is it normal for DOM to output everything in UTF8 without an ability to > influence this? Yes. > I figured that it wouldn't be a UTF8 problem because it > outputs 2 bytes, and I thought UTF8 was just 1 byte (henc

Re: [PHP-DEV] quite a big bug in DOM

On 9/16/05, Ron Korving <[EMAIL PROTECTED]> wrote: > Damn.. I feel stupid now... Sorry guys. > Is it normal for DOM to output everything in UTF8 without an ability to > influence this? For the record, DOM does not output anything using UTF-8, it does convert the input to UTF-8. It's a slighty diff

Re: [PHP-DEV] Re: Reference handling change and PHP 4.4.0

On Thu, 15 Sep 2005, Todd Ruth wrote: > Aha! That was the inspiration I needed to get the right > combination of "&"s. The following bit of code behaves > differently under 4.3 vs 4.4: > > function f(&$a) { return $a; } > $x = array('a','b','c'); > foreach (array_keys($x) as $k) { >// I th

Re: [PHP-DEV] PHP 6.0 Wishlist

This one time, at band camp, "Ron Korving" <[EMAIL PROTECTED]> wrote: > The problem with this would be that it can't be decided on a per-case basis, > but only for the whole switch, which would make the execution slower. That's > why I'd prefer a "regcase", but I guess this can be considered ugly

[PHP-DEV] big reference bug in (at least) PHP 5.0.5

My apologies for my DOM-mistake today, but right now I came across something that totally stunned me. It's a total paradox situation that just has to be one of the biggest bugs I've ever come across in PHP. Personally, I think it's rather high-priority because it's an engine problem, and not an iss

Re: [PHP-DEV] big reference bug in (at least) PHP 5.0.5

On 16.09.2005 16:29, Ron Korving wrote: My apologies for my DOM-mistake today, but right now I came across something that totally stunned me. It's a total paradox situation that just has to be one of the biggest bugs I've ever come across in PHP. Personally, I think it's rather high-priority beca

Re: [PHP-DEV] PHP 6.0 Wishlist

You mean that preg_match() would match an ordinary string just fine? I wouldn't prefer that for performance reasons. I'd like to choose per case how I want the matching done (regexp or not). Ron "Kevin Waterson" <[EMAIL PROTECTED]> schreef in bericht news:[EMAIL PROTECTED] > This one time, at ban

Re: [PHP-DEV] big reference bug in (at least) PHP 5.0.5

Okay, you're right that it starts working fine when I rename the $item to $blah, but your explanation doesn't make much sense. After the first foreach, $item points to the last one, that I already figured. If you ask me, the second foreach should replace the instance of $item, not overwrite it. Bu

Re: [PHP-DEV] big reference bug in (at least) PHP 5.0.5

Ron Korving wrote: >The last item in the array is replaced, not by the first one of the second >foreach, but by the item before the last item. That just doesn't make sense >at all. > > This is where you're going wrong (and where I was going wrong in thinking about this before Antony's message).

Re: [PHP-DEV] big reference bug in (at least) PHP 5.0.5

Good point. I think it's somehow undesired behavior, but what can one do to change this? I guess it somehow is desired behavior... My bad I guess, Ron "Matthew Charles Kavanagh" <[EMAIL PROTECTED]> schreef in bericht news:[EMAIL PROTECTED] > Ron Korving wrote: > > >The last item in the array is

Re: [PHP-DEV] Bogusing bot (Was: [PHP-DEV] Reference handling change and PHP 4.4.0)

Hello Jani, Jani, thanks for the work! If it wasn't you we all had to do it and everybody had to keep track. Having you doing all the checks is quit econvenient (for us). best regards marcus Thursday, September 15, 2005, 1:25:56 PM, you wrote: > On Thu, 15 Sep 2005, Leigh Makewell wrote: >>

[PHP-DEV] Re: HEAD == PHP 7 (Was: Re: [PHP-DEV] PHP6, Unicode for language functions, classes,methods, vars names)

I don't think that's feasible as it makes development even harder. I don't think Unicode support is that far off. Most of the core work is done. The more people can help with upgrading the functions the better... I'm off for the weekend Might find some Internet connection at some point. And

Re: [PHP-DEV] Re: HEAD == PHP 7 (Was: Re: [PHP-DEV] PHP6, Unicode for language functions, classes,methods, vars names)

On 9/16/05, Andi Gutmans <[EMAIL PROTECTED]> wrote: > I don't think that's feasible as it makes development even harder. > I don't think Unicode support is that far off. Most of the core work > is done. The more people can help with upgrading the functions the better... I agree here, as far as """

Re: [PHP-DEV] Re: HEAD == PHP 7 (Was: Re: [PHP-DEV] PHP6, Unicode for language functions, classes,methods, vars names)

On 9/16/05, Pierre Joye <[EMAIL PROTECTED]> wrote: > From my side, after some cleanup, I should be UC ready pretty soon, > but that is all post pear-1.4.0/5.1.0 stories :) + ext/gd -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php

Re: [PHP-DEV] Re: Reference handling change and PHP 4.4.0

Wasn't part of the "negotiation" when 4.4 was created that the behavior would be the same as 4.3 (excluding anything that happened because of a memory corruption)? (I'm not counting the notices as behavior.) I don't see how it can be argued that "$y =& ..." leaving $y connected to it's old buddie

Re: [PHP-DEV] Bogusing bot (Was: [PHP-DEV] Reference handling change and PHP 4.4.0)

Danke, Jani. Cheers, John On Fri, 2005-09-16 at 16:29 +0200, Marcus Boerger wrote: > Hello Jani, > > Jani, thanks for the work! If it wasn't you we all had to do it and > everybody had to keep track. Having you doing all the checks is quit > econvenient (for us). > > best regards > marcus >

[PHP-DEV] Re: Thanks Jani

Gracis senor Taskinen por todos anos. Besos! - Original Message - From: "John Coggeshall" <[EMAIL PROTECTED]> Newsgroups: php.internals To: "Marcus Boerger" <[EMAIL PROTECTED]> Cc: "Jani Taskinen" <[EMAIL PROTECTED]>; "Leigh Makewell" <[EMAIL PROTECTED]>; Sent: Friday, September 16,

[PHP-DEV] Re: Bogusing bot (Was: [PHP-DEV] Reference handling change and PHP 4.4.0)

Over, my, dead, smoking, carcass. --Jani On Fri, 16 Sep 2005, Scott MacVicar wrote: Hi, We had complaints about Bogus recently from customers and opted to rename this category "Not a Bug" which has went down a lot better and there is less backlash when we use this category. May

[PHP-DEV] Session id

Hello, first I'm inquiring about this: http://bugs.php.net/bug.php?id=23681 Currently (in 5.0.3 at least), if someone makes a request with invalid session id characters, Warnings are output: PHP Warning: session_start(): The session id contains illegal characters, valid characters are a-z, A-Z,

[PHP-DEV] Re: Segfault

Well I did try to use it in RINIT, but PHP just wasn't RINIT so I figured why not put it in MINIT ""Sara Golemon"" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] > > That's not where it segfaults. The function works perfectly once. If I > > attempt to exit / > > die or call that f

[PHP-DEV] Re: Segfault

Well I did try to use it in RINIT, but PHP just wasn't RINIT so I figured why not put it in MINIT. And I solved the problem, I guess I should have been more careful when reading the PHP API tutorials, I used malloc instead of emalloc, so malloc was causing gcc to miscalculate its size or make i

Re: [PHP-DEV] Re: Bogusing bot (Was: [PHP-DEV] Reference handling change and PHP 4.4.0)

On Thu, 15 Sep 2005, Leigh Makewell wrote: > Well then I suggest you get out there and find out what you are doing > wrong because there is an increasing number of people out there who are > not happy with how their bugs are being treated. > This is a good place to start. > http://www.sitepoint.co

Re: [PHP-DEV] Re: Bogusing bot (Was: [PHP-DEV] Reference handlingchange and PHP 4.4.0)

Nicely said, Adam. - Original Message - From: "Adam Maccabee Trachtenberg" <[EMAIL PROTECTED]> To: "Leigh Makewell" <[EMAIL PROTECTED]> Cc: Sent: Saturday, September 17, 2005 1:48 AM Subject: Re: [PHP-DEV] Re: Bogusing bot (Was: [PHP-DEV] Reference handlingchange and PHP 4.4.0) > On Th

Re: [PHP-DEV] Re: Segfault

RG wrote: Well I did try to use it in RINIT, but PHP just wasn't RINIT so I figured why not put it in MINIT. ... > I used malloc instead of emalloc, so malloc was causing gcc to miscalculate its size or make it quit with an error. both claims above don't make *any* sense to me, making m