Hello,
Is the link in the changelog pointing to the wrong bug? Seems mb related but
speaks of mysqli. Just something small I noticed.
-Chris
On Thu, Aug 7, 2008 at 1:47 PM, Derick Rethans <[EMAIL PROTECTED]> wrote:
> Hello,
>
> The PHP development team would like to announce the immediate
> ava
Hello,
The PHP development team would like to announce the immediate
availability of PHP 4.4.9. It continues to improve the security and the
stability of the 4.4 branch and all users are strongly encouraged to
upgrade to it as soon as possible. This release wraps up all the
outstanding patches
On Thursday 07 August 2008 21:52:37 Rasmus Lerdorf wrote:
> Felipe Pena wrote:
> > Em Qui, 2008-08-07 às 20:55 +0200, Hannes Magnusson escreveu:
> >> On Thu, Aug 7, 2008 at 20:20, Rasmus Lerdorf<[EMAIL PROTECTED]> wrote:
> >>> Christian Stocker wrote:
> Hi
>
> Since quite some time
Felipe Pena wrote:
Em Qui, 2008-08-07 às 20:55 +0200, Hannes Magnusson escreveu:
On Thu, Aug 7, 2008 at 20:20, Rasmus Lerdorf<[EMAIL PROTECTED]> wrote:
Christian Stocker wrote:
Hi
Since quite some time (weeks), I have this very strange and annoying
include bug in 5.3-dev and now I think is t
Em Qui, 2008-08-07 às 20:55 +0200, Hannes Magnusson escreveu:
> On Thu, Aug 7, 2008 at 20:20, Rasmus Lerdorf <[EMAIL PROTECTED]> wrote:
> > Christian Stocker wrote:
> >>
> >> Hi
> >>
> >> Since quite some time (weeks), I have this very strange and annoying
> >> include bug in 5.3-dev and now I thin
Hi all,
After speaking with several people about their todo items [1],
Johannes and I have settled on the 28th of August for the alpha2
release. We will package on the 27th. Seems like we have a good chance
for getting the open items completed by then.
Note that things that do not make it
On Thu, Aug 7, 2008 at 20:20, Rasmus Lerdorf <[EMAIL PROTECTED]> wrote:
> Christian Stocker wrote:
>>
>> Hi
>>
>> Since quite some time (weeks), I have this very strange and annoying
>> include bug in 5.3-dev and now I think is the time to report it :)
>>
>> The reproducable script is here:
>>
>> h
Christian Stocker wrote:
Hi
Since quite some time (weeks), I have this very strange and annoying
include bug in 5.3-dev and now I think is the time to report it :)
The reproducable script is here:
http://trash.chregu.tv/include-bug.php.txt
In short, when I have
foo/alpha (empty)
bar/alpha/ba
Further to my comment on http://bugs.php.net/bug.php?id=45132
Many servers appear to have LANG set to some non-UTF-8 character set.
With ext/standard/exec.c version 1.127, released in PHP 5.2.6, this
means that apps that try to send UTF-8 to shell arguments are broken.
The "invalid" characters are
Hi Johannes,
The TODOs seem to be quite outdated, the Upgrading guides for 5.0, 5.1
and 5.2 are part of the documentation meanwhile. 5.3 will get a new one.
Can we hang on to the UPGRADING file please, it's not actually a
version-specific file :) just the contents need updating.
Thanks,
-
I think the TODOs can be safely killed and a single one restarted
based on the release wiki.
On 7-Aug-08, at 11:13 AM, Johannes Schlüter wrote:
Hi,
the php-src/ dir is quite filled with outdated READMEs and TODOs, any
objection to remove these files:
README.PHP4-TO-PHP5-THIN-CHANGES
README
Johannes Schlüter wrote:
> Hi,
>
> README.WIN32-BUILD-SYSTEM - does this require updating for the new build
> infrastructure?
>
> johannes
>
Yes it does, it's on the todo list
Thanks,
Elizabeth
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.n
Hi!
So what is your point here? You say we failed a few times to be consistent
in the past, so today we should do everything to prevent anything that
looks like consistency? Do you read what you write?
My point is that changing constructs that work differently to look the
same because somebod
On Thursday 07 August 2008 17:01:52 Lukas Kahwe Smith wrote:
> On 07.08.2008, at 16:59, Arnaud Le Blanc wrote:
> > Hi,
> >
> > On Thursday 07 August 2008 16:48:30 Johannes Schlüter wrote:
> >> Hi,
> >>
> >> On Thu, 2008-08-07 at 13:07 +, "Antony Dovgal" wrote:
> >>> tony2001 Thu Aug 7
Hi,
the php-src/ dir is quite filled with outdated READMEs and TODOs, any
objection to remove these files:
README.PHP4-TO-PHP5-THIN-CHANGES
README.QNX
README.UPDATE_5_2
README.Zeus
TODO
TODO-5.1
TODO-PHP5
UPGRADING
The TODOs seem to be quite outdated, the Upgrading guides for 5.0, 5.1
and 5.2 ar
On 07.08.2008, at 16:59, Arnaud Le Blanc wrote:
Hi,
On Thursday 07 August 2008 16:48:30 Johannes Schlüter wrote:
Hi,
On Thu, 2008-08-07 at 13:07 +, "Antony Dovgal" wrote:
tony2001Thu Aug 7 13:07:07 2008 UTC
Removed files:
/php-src/ext/pcntl EXPERIMENTAL
Log:
re
Hi,
On Thursday 07 August 2008 16:48:30 Johannes Schlüter wrote:
> Hi,
>
> On Thu, 2008-08-07 at 13:07 +, "Antony Dovgal" wrote:
> > tony2001Thu Aug 7 13:07:07 2008 UTC
> >
> > Removed files:
> > /php-src/ext/pcntl EXPERIMENTAL
> > Log:
> > remove EXPERIMENTAL flag
Hi,
On Thu, 2008-08-07 at 13:07 +, "Antony Dovgal" wrote:
> tony2001 Thu Aug 7 13:07:07 2008 UTC
>
> Removed files:
> /php-src/ext/pcntlEXPERIMENTAL
> Log:
> remove EXPERIMENTAL flag
The EXTENSIONS file says
EXTENSION: pcntl
MAINTENA
On 07.08.2008, at 16:29, Hannes Magnusson wrote:
On Thu, Aug 7, 2008 at 16:17, Ulf Wendel <[EMAIL PROTECTED]> wrote:
He explained to me that using SET NAMES is what is not recommended
when
using libmysql because:
- there is no verification if the client knows the charset
- the internal mysq
Hannes Magnusson wrote:
On Thu, Aug 7, 2008 at 16:17, Ulf Wendel <[EMAIL PROTECTED]> wrote:
He explained to me that using SET NAMES is what is not recommended when
using libmysql because:
- there is no verification if the client knows the charset
- the internal mysql->charset field will not b
On Thu, Aug 7, 2008 at 16:17, Ulf Wendel <[EMAIL PROTECTED]> wrote:
> He explained to me that using SET NAMES is what is not recommended when
> using libmysql because:
>
> - there is no verification if the client knows the charset
> - the internal mysql->charset field will not be set properly
Is
Ulf Wendel schrieb:
I don't recall why I added "usage not recommended" to the test. Let me
check with Georg. He had some concerns on the function as far as I
remember.
I checked with Georg. My memories regarding Georg's position are totally
wrong. He once introduced mysql_set_charset to the M
On 02.08.2008 21:03, Maciek Sokolewicz wrote:
Right, so, if this _is_ still considered experimental, then we should
fix it in the documentation; and if it's not, we should fix the
configure script.
Fixed (removed the experimental status).
--
Wbr,
Antony Dovgal
--
PHP Internals - PHP Runtim
Sorry, I had not thought about that. I just checked with the example given in
the bug report and it's effectively slower (~25% on this expression).
On Thursday 07 August 2008 14:35:12 Nuno Lopes wrote:
> No!
> Last time I benchmark it, it has about 100x slower, so I don't think so..
> If you nee
No!
Last time I benchmark it, it has about 100x slower, so I don't think so.. If
you need to match large amounts of data, just increase the stack size.
ulimit is your friend :)
Nuno
- Original Message -
From: "Arnaud Le Blanc" <[EMAIL PROTECTED]>
To:
Sent: Thursday, August 07, 200
Hi,
PCRE can be highly recursive [1] and this can cause segmentation faults [2].
This is a known problem and the pcre ini settings avoids the segfaults, but
the execution of the expression will fail anyway.
PCRE has a NO_RECURSE flag which makes the match() internal function no
recursive and a
On Thu, Aug 7, 2008 at 03:18, Christian Stocker
<[EMAIL PROTECTED]> wrote:
> According to http://bugs.php.net/bug.php?id=45044 I'm not the only one with
> that problem and it really introduces a lot of issues.
You are not the onlyone.
I'm pretty sure I mailed about this to internals@ few weeks ago
Hello Stanislav,
Wednesday, August 6, 2008, 6:42:48 PM, you wrote:
> Hi!
>> What a nitpicking :) So would I say that the global statement is
>> inconsistent with static because it doesn't allow assignments within the
>> statement :p
> Sure it is. That's just another thing to show all this "co
On Thursday 07 August 2008 01:50:06 Johannes Schlüter wrote:
> On Wed, 2008-08-06 at 21:00 +0200, Arnaud Le Blanc wrote:
> > > > btw. I just noticed chroot() calls this
> > > > realpath_cache_clean()..intentional?
>
> I'd assume that, as /foo inside a chroot is different from /foo
> outside...
>
>
Hi Marcus,
In case you really like this syntax, you can try to implement patch and
propose it to @internals.
I don't like it just because it seems wrong for me, so personally I'll
object your patch.
Thanks. Dmitry.
Marcus Boerger wrote:
Hello Dmitry,
Tuesday, August 5, 2008, 1:28:32 PM,
30 matches
Mail list logo
