Didn't say I thought it was going to happen, just that I rather take a
step "back" then a step "forward" if any movement at all was going to
happen.
John
On Wed, 2005-08-31 at 17:15 -0400, Adam Maccabee Trachtenberg wrote:
> Let's please stop breaking things just because we find them
> aesthetica
Done. All distros should have at least 2.6.8. Most have 2.6.16 or above..
--Jani
On Wed, 31 Aug 2005, Rob Richards wrote:
I would suggest bumping up the libxm2 minimum version to 2.6.8. Had forgotten
about this until a recent bug, but 2.6.6 and 2.6.7 can cause memory corruption
that
On Wed, 31 Aug 2005, Derick Rethans wrote:
> On Tue, 30 Aug 2005, Zeev Suraski wrote:
>
> > For those of you who submitted patches to 5.1 since RC1 - do you believe
> > that
> > we need another RC or can we go ahead and roll 5.1 final and run a sanity
> > test
> > for 24 hours? I went over the
On Wed, 31 Aug 2005, steve wrote:
At any rate, there are two problems:
1) That the newly thrown exception blows up into a fatal error that
doesn't list the file or line number.
Example code?
2) mysqli is unloaded(!?) (or appears to be) before the the user's
shutdown function is called. T
On Thu, 1 Sep 2005, Derick Rethans wrote:
On Wed, 31 Aug 2005, Derick Rethans wrote:
On Tue, 30 Aug 2005, Zeev Suraski wrote:
For those of you who submitted patches to 5.1 since RC1 - do you believe that
we need another RC or can we go ahead and roll 5.1 final and run a sanity test
for 24 ho
On Wed, 31 Aug 2005, Ondrej IvaniÄ wrote:
Jani Taskinen wrote:
On Tue, 30 Aug 2005, Andrei Zmievski wrote:
On Aug 30, 2005, at 10:30 AM, Rasmus Lerdorf wrote:
Also, I see the following 6 failed test cases on my Linux box:
-Bug #16069 [ext/iconv/tests/bug16069.phpt]
According to the last
At 11:31 01/09/2005, Derick Rethans wrote:
On Wed, 31 Aug 2005, Derick Rethans wrote:
> On Tue, 30 Aug 2005, Zeev Suraski wrote:
>
> > For those of you who submitted patches to 5.1 since RC1 - do you
believe that
> > we need another RC or can we go ahead and roll 5.1 final and run a
sanity tes
> It has more to do with problems with encapsulation and visibility.
> Frederik made a nice summary of that, he will reply here:
Ok, here goes:
The way I see it properties in PHP should do the following:
1. Make it possible to override behavior when accessing properties
2. easy access to
> So for reasons of performance, simplicity, and practicality, I would
> say str_pad should:
>
> 1) of course surrogates must not be broken up
> 2) The pad string can have combining characters.
> 3) The length the user specifies should be a character count.
I presume that "character" above refers
On Sep 1, 2005, at 6:32 AM, Rolland Santimano wrote:
4) The string can be truncated to the user's requested character
length. The string will be trimmed from the right one unicode utf-8
character (not grapheme, not byte) at a time until the length limit
is
met. (So a combining character is on
On 9/1/05, Jani Taskinen <[EMAIL PROTECTED]> wrote:
> __destruct()'s are called before the user registered shutdown functions.
> This will not change so don't bother reporting a bug about this.
Eew. Is this a change in 5.0.5? Seemed not to be a problem in 5.0.4.
Not that it matters, as l
Hey Markus,
As we're waiting for Wez to commit fixes, and this patch is just
adding a new function (and not messing with existing functionality),
I think it's OK to include...
We'll have to roll RC2.
Rasmus, Wez - Any idea about timing for PDO? Are all these bugs
crucial to fix for 5.1?
And
I seem to have lost the patch, can someone send it to me again and I'll
apply it? Andi it's okay I include this in 5.1?
John
On Thu, 2005-09-01 at 21:52 -0700, Andi Gutmans wrote:
> Hey Markus,
>
> As we're waiting for Wez to commit fixes, and this patch is just
> adding a new function (and not
Andi Gutmans wrote:
> Hey Markus,
>
> As we're waiting for Wez to commit fixes, and this patch is just adding
> a new function (and not messing with existing functionality), I think
> it's OK to include...
> We'll have to roll RC2.
> Rasmus, Wez - Any idea about timing for PDO? Are all these bugs
--- Andrei Zmievski <[EMAIL PROTECTED]> wrote:
>
> >> 4) The string can be truncated to the user's requested character
> >> length. The string will be trimmed from the right one unicode
> >> utf-8 character (not grapheme, not byte) at a time until the
length
> >> limit is met. (So a combining char
Hi,
attached the initial email to the list with the patch.
I've been running this now since July in a web crawling application
which runs every day and had no problems. The application is CLI based
and runs for some hours everytime without any sign of memory leaking.
However my c knowledge is
16 matches
Mail list logo
