Ulf Wendel wrote:
If mysqlnd turns out to be stable enough during the PHP 5.3 test phase,
PHP 5.3+ may use mysqlnd as a default. There is no need to download an
extra library when using 5.3.
Lukas, this is not affecting PHP 5.3 as long as mysqlnd is
stable/fast/... enough to be used as a defa
On Thursday 17 July 2008 6:23:31 pm Moriyoshi Koizumi wrote:
> Hi,
>
> Attached are the patches that allow the "use" statement that was
> introduced with closures to appear within every function statement
> except method definitions. I think this feature is a good addition
> because it resolves inc
Hi,
This is regarding CVS account request.
I have participated in testfest and contributed some PHPT tests for GD related
functions.
They have already been reviewed by Pierre and committed by Zoe.
Refer following testfest tasks
http://testfest.php.net/index.php?do=details&task_id=5
http://testfe
Hi all,
I've been struggling a bit with Apache tonight. I'd hoped to send real
patches at the end of it, but...
I got sapi/apache to build by adding a direct include for zend_globals.h to
php_apache_http.h. I have no idea why the apache sapi would suddenly want
that, I just know it showed n
Hi,
Attached are the patches that allow the "use" statement that was
introduced with closures to appear within every function statement
except method definitions. I think this feature is a good addition
because it resolves inconsistency between closures and unticked
functions. In a nutshe
On 17.07.2008, at 21:29, Felipe Pena wrote:
felipe Thu Jul 17 19:29:34 2008 UTC
Modified files: (Branch: PHP_5_3)
/ZendEngine2 zend_compile.c
/ZendEngine2/tests bug43027.phpt jump12.phpt
/php-src/ext/standardbasic_functions.c
/php-src/ext/standard/t
Stanislav Malyshev escreveu:
Hi!
Of course its predictable. What Greg meant is "error prone". The
difference is if we want to by default lower the chance of programming
mistakes or ensure maximum performance with little effort for users
with autoload (and long include path lists).
I think s
Hi!
Of course its predictable. What Greg meant is "error prone". The
difference is if we want to by default lower the chance of programming
mistakes or ensure maximum performance with little effort for users with
autoload (and long include path lists).
I think silent performance disaster is
On 17.07.2008, at 19:57, Stanislav Malyshev wrote:
Hi!
In other words, with the current implementation, you can just do
"use Foo::Exception;" and it works, but if you *forget* to do the
use statement, you can get unpredictable behavior with no warning
until your
You get previctable beh
Hi!
There is nothing wrong with autoload. However it adds overhead so if you
want super duper high performance, you use explicit includes/requires
with absolute paths instead.
In most cases, it is not practical - code with autoload in 99.9% of
cases would be more robust, more maintainable an
On 17.07.2008, at 20:03, Stanislav Malyshev wrote:
autoload that is). At the same time people who care about
performance can still work around this behavior (then again those
that care about optimizations on this level probably do not use
autload to begin with).
What's wrong with autoloa
Hi!
Greg's argument seems sound to me. With the proposed change errors are
less likely and more transparent in case they happen (for people using
No, they won't be transparent at all. If you use Exception and forget to
put "use ::Exception" in each and every of your files, you get
exhaustiv
Hi!
In other words, with the current implementation, you can just do "use
Foo::Exception;" and it works, but if you *forget* to do the use
statement, you can get unpredictable behavior with no warning until your
You get previctable behavior in all cases, there's no randomness in the
engine.
On 17.07.2008, at 19:38, Jochem Maas wrote:
1. I don't know .phpt (I can solve this)
its quite easy. if you have questions either send them to [EMAIL PROTECTED]
or join us in #php.pecl on efnet or #phptestfest on freenode
respectively.
2. I have no idea what to expect and therefore tes
Thank you everyone for you replies, apparently I know a little
more than I thought in general and also a little more than this
morning. :-)
rgds,
Jochem
Andi Gutmans schreef:
There are some things I mention in this blog entry re: why I think
...
--
PHP Internals - PHP Runtime Development Mail
Marcus Boerger schreef:
Hello Jochem,
...
I just posted another mail to internals in which I attempt to detail the
__autoload behaviour 'issues' ... it includes something that wants to be a
test suite when it grows up ... it might help someone to investage/determine
what __autoload() does/sh
Hello,
Ok, that's why I said that I didn't know what to do with these conversions. At
now I just left the E_NOTICE errors.
Regards
> Hello Arnaud,
>
> I will commit it afte I have reviewed and changed it a bit. Right now you
> ignore conversoin errors. I'll change this to throw exceptions to
There are some things I mention in this blog entry re: why I think
multi-process architecture is not a bad thing even with where CPUs are
going:
http://tinyurl.com/3eyfth
This was obviously a heated discussion and I'd appreciate if you have
flames/comments to send them to me directly and/or on the
Hi!
a, what are the ramifications of having to run php without threading
when we live in a world that's increasingly moving towards
multi-core/multi- CPU systems?
I'd say next to none, since multi-CPU systems are perfectly capable of
running multiple processes and PHP lives in the context of
On Thu, Jul 17, 2008 at 12:40 PM, Stanislav Malyshev <[EMAIL PROTECTED]> wrote:
> Hi!
>
>> is it possible to add custom (more user-friendly) error-message in this
>> case?
>
> I don't know. So far we never had custom user-friendly error messages in
> parser. If you want to do it and know how, you
Hi all,
Replying to this OLD message about the ZEND_SIGNED_MULTIPLY_LONG() change...
It's just a small thing, but it's been on the TODO for a while, so I
attempted to correct the issue with my original patch that used "long long"
type, which wasn't available on the older MSVC versions, etc. I cre
Ulf Wendel schrieb:
Ulf Wendel schrieb:
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 as
Hello Jochem,
Thursday, July 17, 2008, 12:03:42 PM, you wrote:
> Hi Marcus,
> Marcus Boerger schreef:
>> 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.
> The thing is under quite a few
Ulf Wendel schrieb:
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 th
On Thu, Jul 17, 2008 at 12:47 PM, Ulf Wendel <[EMAIL PROTECTED]> wrote:
> although you do not read my blog you seem to be sure about its contents: bug
> reports, improvements and RFCs. Stuff thatshould have gone to the
> development lists.
>
> I proved that I did file PDO bugs and work on PDO bugs
Pierre Joye schrieb:
hi,
On Wed, Jul 16, 2008 at 7:27 PM, Ulf Wendel <[EMAIL PROTECTED]> wrote:
What improvements or RFC's did I blog about instead of sending them to the
PHP development list. Its just not obvious to me.
No idea, and that's the problem. I do read the bug reports, not your bl
Jochem Maas wrote:
David Zülke schreef:
Am 17.07.2008 um 11:36 schrieb Mario Brandt:
I made a test on my console (cmd.exe)
ENV: WinXP SP 3 all updates, PHP 5.2.6 / PHP 5.2.6 non thread safe
(NTS)
Intel Celeron 2.4 GHz 1 GB DDR Ram
It showed that the non thread safe is faster than the thr
David Zülke schreef:
Am 17.07.2008 um 11:36 schrieb Mario Brandt:
I made a test on my console (cmd.exe)
ENV: WinXP SP 3 all updates, PHP 5.2.6 / PHP 5.2.6 non thread safe (NTS)
Intel Celeron 2.4 GHz 1 GB DDR Ram
It showed that the non thread safe is faster than the thread safe
version.
And
hi,
On Thu, Jul 17, 2008 at 11:36 AM, Mario Brandt <[EMAIL PROTECTED]> wrote:
> I made a test on my console (cmd.exe)
> ENV: WinXP SP 3 all updates, PHP 5.2.6 / PHP 5.2.6 non thread safe (NTS)
> Intel Celeron 2.4 GHz 1 GB DDR Ram
>
> It showed that the non thread safe is faster than the thread sa
Hi,
That should be correct as there is no time spent keeping internal
variables thread safe.
Mario Brandt skrev:
I made a test on my console (cmd.exe)
ENV: WinXP SP 3 all updates, PHP 5.2.6 / PHP 5.2.6 non thread safe (NTS)
Intel Celeron 2.4 GHz 1 GB DDR Ram
It showed that the non thread sa
Am 17.07.2008 um 11:36 schrieb Mario Brandt:
I made a test on my console (cmd.exe)
ENV: WinXP SP 3 all updates, PHP 5.2.6 / PHP 5.2.6 non thread safe
(NTS)
Intel Celeron 2.4 GHz 1 GB DDR Ram
It showed that the non thread safe is faster than the thread safe
version.
And your point/questi
Hi Marcus,
Marcus Boerger schreef:
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.
The thing is under quite a few circumstances the Exceptions do bubble up,
and there is another issue with __au
I made a test on my console (cmd.exe)
ENV: WinXP SP 3 all updates, PHP 5.2.6 / PHP 5.2.6 non thread safe (NTS)
Intel Celeron 2.4 GHz 1 GB DDR Ram
It showed that the non thread safe is faster than the thread safe version.
NTS
Benchmark Time Peak MemoryPeak Memory (Real)
-
hi,
On Wed, Jul 16, 2008 at 7:27 PM, Ulf Wendel <[EMAIL PROTECTED]> wrote:
> What improvements or RFC's did I blog about instead of sending them to the
> PHP development list. Its just not obvious to me.
No idea, and that's the problem. I do read the bug reports, not your blog.
--
Pierre
http
hello people,
I believe there is something wrong (or inconsitent) with the way __autoload()
behaves. at the least the current docs don't reflect what I'm seeing.
1. the docs state:
"Exceptions thrown in __autoload function cannot be caught in the catch
block and results in a fatal erro
Hi!
is it possible to add custom (more user-friendly) error-message in this case?
I don't know. So far we never had custom user-friendly error messages in
parser. If you want to do it and know how, you can propose it, but
then I guess other parser errors should get same treatment.
--
Stani
On Thu, Jul 17, 2008 at 10:35 AM, Stanislav Malyshev <[EMAIL PROTECTED]> wrote:
> Hi!
>
>> I think it may be more productive to disallow it now, instead of
>> bogusifying bug reports and dealing with confused users later. My 2ct.
>
> I don't think wasting effort on introducing artificial restrictio
Hello Arnaud,
I will commit it afte I have reviewed and changed it a bit. Right now you
ignore conversoin errors. I'll change this to throw exceptions to be inline
with other code. However I am in Tel Aviv right now for a company work
meeting, so I have little time this week.
marcus
Wednesday,
Hi!
This has nothing to do with dl(). mysqli was loaded in php.ini via
extension=mysqli.so
Oh, I missed that point. Anyway, it sounds logical that all resources
should be freed before modules are unloaded, not the reverse.
--
Stanislav Malyshev, Zend Software Architect
[EMAIL PROTECTED]
39 matches
Mail list logo
