Hello Jochem,
seems like we have quite some nice additions to the manual here in this
thread. Now to the real issue, Exceptions don't bubble up. That is they
are simply ignored. And once all __autoload work is done and the class
still doesn't exist an E_ERROR is issued. The work around for
Hello Lukas,
Monday, July 14, 2008, 2:58:13 PM, you wrote:
Hi,
I am about to move all to be discussed items [1] to the future PHP
release section (so after 5.3):
1) userspace streams filter that acts as a default filter through
which require/include read their files (Sebastian, Sara)
Hi there,
(Yeah, it's been a long time.. Many of you might well have thought
I'm dead :)
This time I want to revisit the following issue:
http://article.gmane.org/gmane.comp.php.devel/50681
Is there any point to disable mbregex alone instead of disabling the
whole mbstring stuff? Unless the
Lukas Kahwe Smith wrote:
Hi,
I am about to move all to be discussed items [1] to the future PHP
release section (so after 5.3):
1) userspace streams filter that acts as a default filter through which
require/include read their files (Sebastian, Sara)
2) XMLWriter: Add writeNode([xmlreader
hi Marcus,
On Mon, Jul 14, 2008 at 11:15 PM, Marcus Boerger [EMAIL PROTECTED] wrote:
2) XMLWriter: Add writeNode([xmlreader obj]), allow to create a push/
pull parser
should be easy enough and is simply a new function in an ext, can't just
somebody do it?
It is not hard but not a small
On 15.07.2008, at 13:25, Pierre Joye wrote:
hi Marcus,
On Mon, Jul 14, 2008 at 11:15 PM, Marcus Boerger [EMAIL PROTECTED]
wrote:
2) XMLWriter: Add writeNode([xmlreader obj]), allow to create a
push/
pull parser
should be easy enough and is simply a new function in an ext, can't
Hello Moriyoshi,
Tuesday, July 15, 2008, 1:05:35 PM, you wrote:
Hi there,
(Yeah, it's been a long time.. Many of you might well have thought
I'm dead :)
This time I want to revisit the following issue:
http://article.gmane.org/gmane.comp.php.devel/50681
Is there any point to disable
Hi Lukas,
Lukas Kahwe Smith wrote:
Hi,
I am about to move all to be discussed items [1] to the future PHP
release section (so after 5.3):
2) XMLWriter: Add writeNode([xmlreader obj]), allow to create a
push/pull parser
I also don't think I would be able to find the time to get this done
Hi Marcus,
Marcus Boerger wrote:
Hello Andrey,
Tuesday, July 15, 2008, 3:12:27 PM, you wrote:
andrey Tue Jul 15 13:12:27 2008 UTC
Modified files:
/php-src/ext/mysql php_mysql.c
/php-src/ext/mysqli mysqli.c
/php-src/ext/mysqlndmysqlnd.c
On Tue, Jul 15, 2008 at 4:10 PM, Andrey Hristov [EMAIL PROTECTED] wrote:
bzr stands for Bazaar. We have internally switched from svn to bazaar. There
is also public repository
bzr clone lp:~andrey-mysql/php-mysqlnd/trunk
I think Ulf will soon write a blog entry about it.
I do not like to
Pierre Joye schrieb:
Drop the launchpad and use php's cvs. We have actually two development
branches (5.3 until the 24th and HEAD) and PECL. The latter let you
experiment as much as you wish.
Pierre, you are not in the position to tell us what repository we use
for internal developments and
Ulf Wendel wrote:
Pierre Joye schrieb:
Drop the launchpad and use php's cvs. We have actually two development
branches (5.3 until the 24th and HEAD) and PECL. The latter let you
experiment as much as you wish.
Pierre, you are not in the position to tell us what repository we use
for internal
Hi,
I've noticed a weird behavior when doing file access from PHP:
PHP seems to make an lstat call on each of the parent directories of the
accessed file, for example see this script:
?php
$fp=fopen(/var/www/metacafe/test,r);
fclose($fp);
?
When running with strace -e lstat I see this:
Marcus Boerger wrote:
Hello Moriyoshi,
(just for Derick answered here)
I never liked this. So imo we can simply get rid of this switch and enable
mbregex as soon as there is mbstring to begin with and regex stuff.
Me neither. As far as I know, the switch exists just for historical
reasons.
Hello Ulf,
Tuesday, July 15, 2008, 4:32:10 PM, you wrote:
Pierre Joye schrieb:
Drop the launchpad and use php's cvs. We have actually two development
branches (5.3 until the 24th and HEAD) and PECL. The latter let you
experiment as much as you wish.
Pierre, you are not in the position to
Hello Moriyoshi,
Tuesday, July 15, 2008, 4:58:38 PM, you wrote:
Marcus Boerger wrote:
Hello Moriyoshi,
(just for Derick answered here)
I never liked this. So imo we can simply get rid of this switch and enable
mbregex as soon as there is mbstring to begin with and regex stuff.
Me
Hi Ulf,
On Tue, Jul 15, 2008 at 4:32 PM, Ulf Wendel [EMAIL PROTECTED] wrote:
Pierre Joye schrieb:
Drop the launchpad and use php's cvs. We have actually two development
branches (5.3 until the 24th and HEAD) and PECL. The latter let you
experiment as much as you wish.
Pierre, you are not
On 2008-07-15 16:58, Moriyoshi Koizumi wrote:
Aside from this, what about removing bundled libmbfl and oniguruma from
HEAD and requiring users' using external ones? Now that intl extension
was merged and I don't think it makes sense.
Huge ++ from me, especially regarding oniguruma. If you'd want
Marcus,
Marcus Boerger wrote:
Hello Ulf,
Tuesday, July 15, 2008, 4:32:10 PM, you wrote:
Pierre Joye schrieb:
Drop the launchpad and use php's cvs. We have actually two development
branches (5.3 until the 24th and HEAD) and PECL. The latter let you
experiment as much as you wish.
Pierre,
Pierre,
Pierre Joye wrote:
Hi Ulf,
On Tue, Jul 15, 2008 at 4:32 PM, Ulf Wendel [EMAIL PROTECTED] wrote:
Pierre Joye schrieb:
Drop the launchpad and use php's cvs. We have actually two development
branches (5.3 until the 24th and HEAD) and PECL. The latter let you
experiment as much as you
Pierre,
Pierre Joye wrote:
On Tue, Jul 15, 2008 at 5:42 PM, Ulf Wendel [EMAIL PROTECTED] wrote:
What's your point, what requests are you talking about?
Please ask Johannes, I told them to him live last time we met. If
there is doubts, I will happily repeat them.
I saw one person
Everyone is welcomed to participate in the mysqlnd development and the
extension has seen changes from outside, as well the mysql extensions
and we never complained that someone does it. I just moved the changes
to our internal revision control system, as Bazaar gives us more freedom
to work
Pierre Joye schrieb:
On Tue, Jul 15, 2008 at 5:42 PM, Ulf Wendel [EMAIL PROTECTED] wrote:
What's your point, what requests are you talking about?
Please ask Johannes, I told them to him live last time we met. If
there is doubts, I will happily repeat them.
So, you have one question related
On Tue, Jul 15, 2008 at 7:05 PM, Ulf Wendel [EMAIL PROTECTED] wrote:
Pierre Joye schrieb:
On Tue, Jul 15, 2008 at 5:42 PM, Ulf Wendel [EMAIL PROTECTED] wrote:
What's your point, what requests are you talking about?
Please ask Johannes, I told them to him live last time we met. If
there is
Pierre Joye schrieb:
On Tue, Jul 15, 2008 at 7:05 PM, Ulf Wendel [EMAIL PROTECTED] wrote:
Pierre Joye schrieb:
On Tue, Jul 15, 2008 at 5:42 PM, Ulf Wendel [EMAIL PROTECTED] wrote:
What's your point, what requests are you talking about?
Please ask Johannes, I told them to him live last time
Pierre Joye wrote:
I have no clue if Andrey has combined several fixes in one commit. At this
point I have to rely on him choosing a proper granularity for a commit. Too
large commits can always happen. You can work for a month in your local CVS
copy and commit 100k at one - no difference.
On Tue, Jul 15, 2008 at 7:47 PM, Andrey Hristov [EMAIL PROTECTED] wrote:
Pierre Joye wrote:
I have no clue if Andrey has combined several fixes in one commit. At
this
point I have to rely on him choosing a proper granularity for a commit.
Too
large commits can always happen. You can work
Pierre Joye wrote:
On Tue, Jul 15, 2008 at 7:47 PM, Andrey Hristov [EMAIL PROTECTED] wrote:
Pierre Joye wrote:
I have no clue if Andrey has combined several fixes in one commit. At
this
point I have to rely on him choosing a proper granularity for a commit.
Too
large commits can always happen.
Amir Hardon wrote:
I've noticed a weird behavior when doing file access from PHP:
PHP seems to make an lstat call on each of the parent directories of the
accessed file, for example see this script:
?php
$fp=fopen(/var/www/metacafe/test,r);
fclose($fp);
?
When running with strace -e lstat I
Marcus Boerger schrieb:
Tuesday, July 15, 2008, 4:32:10 PM, you wrote:
Pierre Joye schrieb:
Drop the launchpad and use php's cvs. We have actually two development
branches (5.3 until the 24th and HEAD) and PECL. The latter let you
experiment as much as you wish.
Pierre, you are not in the
Hi list,
I was playing around with namespaces and stumbled across this:
#!/home/steve/php5.3-200807070430/sapi/cli/php
?php
namespace Foo;
use Foo::Bar as Something;
class Bar { }
?
works fine, whereas
#!/home/steve/php5.3-200807070430/sapi/cli/php
?php
namespace Foo;
{
use
On Tue, 2008-07-15 at 11:40 -0700, Rasmus Lerdorf wrote:
Amir Hardon wrote:
I've noticed a weird behavior when doing file access from PHP:
PHP seems to make an lstat call on each of the parent directories of the
accessed file, for example see this script:
?php
On Tue, 15 Jul 2008, Amir Hardon wrote:
On Tue, 2008-07-15 at 11:40 -0700, Rasmus Lerdorf wrote:
That's a realpath() call and it should be getting cached by the
realpath cache, so if you are seeing these on every request, try
increasing your realpath_cache size in your .ini. Without
Amir Hardon wrote:
On Tue, 2008-07-15 at 11:40 -0700, Rasmus Lerdorf wrote:
Amir Hardon wrote:
I've noticed a weird behavior when doing file access from PHP:
PHP seems to make an lstat call on each of the parent directories of the
accessed file, for example see this script:
?php
On Tue, 2008-07-15 at 12:25 -0700, Rasmus Lerdorf wrote:
Amir Hardon wrote:
On Tue, 2008-07-15 at 11:40 -0700, Rasmus Lerdorf wrote:
Amir Hardon wrote:
I've noticed a weird behavior when doing file access from PHP:
PHP seems to make an lstat call on each of the parent directories of
On Jul 15, 2008, at 2:25 PM, Rasmus Lerdorf wrote:
Well, it is used in other places too, like in figuring out _once
paths. Including the same file using different paths still needs
to be caught.
Are you calling clearstatcache() manually anywhere? That blows
away the entire realpath
Hi,
With the impending release of PHP 5.3 and the addition of namespaces
into PHP, there becomes the issue of integrating libraries that are
designed to still support PHP 4 (please, don't turn this into a
discussion about whether they should or not: this _is_ a real issue)
into something
On Tue, 15 Jul 2008, Amir Hardon wrote:
About the issue with the _once, did the patch Derick offered handles
it (I haven't examined it yet). If not, I just need to make sure that
the same file isn't being referenced by two paths and I'm safe right?
It does not do any real path checks, so
Lukas Kahwe Smith wrote:
In our dreams someone would also make PDO a focus area, since the number
of open bugs is getting ridiculous. This is also a call to the general
community to try and help to find a PDO maintainer. In the mean time
people not adapt in C might at least try and plow
On 15.07.2008, at 23:09, Christopher Jones wrote:
Lukas Kahwe Smith wrote:
In our dreams someone would also make PDO a focus area, since the
number
of open bugs is getting ridiculous. This is also a call to the
general
community to try and help to find a PDO maintainer. In the mean
On Tue, Jul 15, 2008 at 02:09:33PM -0700, Christopher Jones wrote:
For PHP 5.3 on, I'd be happy to see the Windows builds of PDO_OCI only
produce php_pdo_oci.dll and no longer also build php_pdo_oci8.dll.
The latter uses an older set of Oracle client libraries that allows
connections to
Hi Rasmus,
Am Dienstag, den 15.07.2008, 11:40 -0700 schrieb Rasmus Lerdorf:
[...]
That's a realpath() call and it should be getting cached by the realpath
cache, so if you are seeing these on every request, try increasing your
realpath_cache size in your .ini. Without checking the realpath,
Lars Strojny wrote:
Hi Rasmus,
Am Dienstag, den 15.07.2008, 11:40 -0700 schrieb Rasmus Lerdorf:
[...]
That's a realpath() call and it should be getting cached by the realpath
cache, so if you are seeing these on every request, try increasing your
realpath_cache size in your .ini. Without
Daniel Convissor wrote:
On Tue, Jul 15, 2008 at 02:09:33PM -0700, Christopher Jones wrote:
For PHP 5.3 on, I'd be happy to see the Windows builds of PDO_OCI only
produce php_pdo_oci.dll and no longer also build php_pdo_oci8.dll.
The latter uses an older set of Oracle client libraries that
Lukas Kahwe Smith wrote:
On 15.07.2008, at 23:09, Christopher Jones wrote:
Lukas Kahwe Smith wrote:
In our dreams someone would also make PDO a focus area, since the
number
of open bugs is getting ridiculous. This is also a call to the general
community to try and help to find a
There is
apc.include_once_override
Optimize include_once() and require_once() calls and avoid the
expensive system calls used.
and
apc.stat
Be careful if you change this setting. The default is for this to be
On which means that APC will stat (check) the script on each request
to see if it has
46 matches
Mail list logo
