George Schlossnagle schrieb:
Thank you, Jani, for all the (mostly) thankless work.
I second that emotion.
--
Sebastian Bergmann http://www.sebastian-bergmann.de/
GnuPG Key: 0xB85B5D69 / 27A7 2B14 09E4 98CD 6277 0E5B 6867 C514 B85B 5D69
--
PHP Internals - PHP Runtime
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 becuase
e.g. C(++) doesn't have a regcase either and it's quite a diversion
Funny solution :) Not very elegant I think (no offence, coz it is a smart
one), but it works. It would be nice if the language provided it.. Another
problem though with my idea (and not your solution) would be that a
regcase would have the PHP syntax rely on an external library.
Ron
James
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
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
To make it extra clear, what is outputted where the nbsp; 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. euml;) seem to have the
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 sure
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
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 nbsp; represents? It's no biggy, but
maybe something to consider.
Ron
--
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 is a
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.
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 @
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
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 PHP7 next
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 (hence
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
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:
?php
function f($a) { return $a; }
$x = array('a','b','c');
foreach (array_keys($x) as $k) {
// I think
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 becuase
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
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
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 band
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.
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
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:
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
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];
internals@lists.php.net
Sent: Friday,
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.
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,
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 function
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
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.
Nicely said, Adam.
- Original Message -
From: Adam Maccabee Trachtenberg [EMAIL PROTECTED]
To: Leigh Makewell [EMAIL PROTECTED]
Cc: internals@lists.php.net
Sent: Saturday, September 17, 2005 1:48 AM
Subject: Re: [PHP-DEV] Re: Bogusing bot (Was: [PHP-DEV] Reference
handlingchange and PHP
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
33 matches
Mail list logo
