Hi Marcus,
see below
Marcus Boerger wrote:
Hello Internals,
please let's not introduce new inconsistencies. Rather lets make new
stuff consistent with old stuff during the alpha phase of 5.3.
1) new keyword 'use'. Semantically it is the same as 'static' or 'global'
so it should be used in
Hi Marcus,
I have no objections against ZE part of the patch.
If you like ext/reflection part please commit the whole patch.
Thanks. Dmitry.
Christian Seiler wrote:
Hi,
http://www.christian-seiler.de/temp/php/2008-07-24-reflection/reflection-closure-fixes-5.3.patch
On Mon, Aug 4, 2008 at 01:29, Davey Shafik [EMAIL PROTECTED] wrote:
Hey,
it has come to my attention that stream_context_get_default() is /grossly/
misnamed, considering
that it can be used (and is the only way) to SET default options. It works
more like ini_set() in that
you pass in the
I'm curious as to how error_log is opened...
Is it opened when an error occurs, as in open/append to, or is the
file handle kept open when the PHP fastcgi process is spawned?
Essentially I want to be able to provide each client their own PHP
error log, i.e.
/home/client1/php-error.log
But I
On Mon, Aug 4, 2008 at 08:55, Dmitry Stogov [EMAIL PROTECTED] wrote:
I don't like multiple namespaces per file too.
As I remember they were introduced by Greg's request related to ext/phar.
May be he already changed his mind.
I don't think anyone but him likes multiple namespaces per file. I
Hi Etienne,
In general the patch looks fine.
The only thing I don't like is explicit declaration of Closure::__invode
method. It won't have proper arg_info.
Thanks. Dmitry.
Etienne Kneuss wrote:
Hello,
On Sat, Aug 2, 2008 at 7:36 PM, Etienne Kneuss [EMAIL PROTECTED] wrote:
Hi,
this is
Hannes Magnusson schrieb:
I don't think anyone but him likes multiple namespaces per file. I do
remember a PhD thesis sized mail from him explaining why multiple
namespaces per file was needed though (can hardly believe anyone read
the whole thing..).
In some deployment processes, multiple PHP
On 04.08.2008, at 10:28, Stefan Priebsch wrote:
Hannes Magnusson schrieb:
I don't think anyone but him likes multiple namespaces per file. I do
remember a PhD thesis sized mail from him explaining why multiple
namespaces per file was needed though (can hardly believe anyone read
the whole
Hello Lukas,
Monday, August 4, 2008, 10:32:26 AM, you wrote:
On 04.08.2008, at 10:28, Stefan Priebsch wrote:
Hannes Magnusson schrieb:
I don't think anyone but him likes multiple namespaces per file. I do
remember a PhD thesis sized mail from him explaining why multiple
namespaces per
Hi,
I will be out of the office until Monday, August 11th on vacation with very
limited access to my emails.
Thanks,
Andi
Hello Dmitry,
Monday, August 4, 2008, 8:55:00 AM, you wrote:
Hi Marcus,
see below
Marcus Boerger wrote:
Hello Internals,
please let's not introduce new inconsistencies. Rather lets make new
stuff consistent with old stuff during the alpha phase of 5.3.
1) new keyword 'use'.
Hello Stanislav,
Monday, August 4, 2008, 7:06:59 AM, you wrote:
Hi!
1) With the interface, the prototype is fixed.
That definitely would not work. Interface could leave __invoke
undefined, though then it'd be more of documentation/attribute purpose
than enforcing having __invoke. But it
Hello Lukas,
Monday, August 4, 2008, 10:49:43 AM, you wrote:
On 04.08.2008, at 10:41, Marcus Boerger wrote:
Hello Lukas,
Monday, August 4, 2008, 10:32:26 AM, you wrote:
On 04.08.2008, at 10:28, Stefan Priebsch wrote:
Hannes Magnusson schrieb:
I don't think anyone but him likes
On Mon, Aug 4, 2008 at 10:32, Lukas Kahwe Smith [EMAIL PROTECTED] wrote:
On 04.08.2008, at 10:28, Stefan Priebsch wrote:
Hannes Magnusson schrieb:
I don't think anyone but him likes multiple namespaces per file. I do
remember a PhD thesis sized mail from him explaining why multiple
Hi,
Andrey Hristov wrote:
isn't that easily solved by using a opcode cache?
I think this is also one of the things you won't have often at hosters.
I guess there's a speedup by having one file and no cache available,
which is the argument here. Question is: where does that leave us :) If
I
PHP 6 Bug Database summary - http://bugs.php.net/
Num Status Summary (67 total -- which includes 26 feature requests)
===[*General Issues]==
26771 Suspended register_tick_funtions crash under threaded webservers
On 04.08.2008, at 10:41, Marcus Boerger wrote:
Hello Lukas,
Monday, August 4, 2008, 10:32:26 AM, you wrote:
On 04.08.2008, at 10:28, Stefan Priebsch wrote:
Hannes Magnusson schrieb:
I don't think anyone but him likes multiple namespaces per file.
I do
remember a PhD thesis sized mail
On 04.08.2008, at 11:42, Andrey Hristov wrote:
Hi,
Lukas Kahwe Smith wrote:
On 04.08.2008, at 10:41, Marcus Boerger wrote:
Hello Lukas,
Monday, August 4, 2008, 10:32:26 AM, you wrote:
On 04.08.2008, at 10:28, Stefan Priebsch wrote:
Hannes Magnusson schrieb:
I don't think anyone but
Hi,
Lukas Kahwe Smith wrote:
On 04.08.2008, at 10:41, Marcus Boerger wrote:
Hello Lukas,
Monday, August 4, 2008, 10:32:26 AM, you wrote:
On 04.08.2008, at 10:28, Stefan Priebsch wrote:
Hannes Magnusson schrieb:
I don't think anyone but him likes multiple namespaces per file. I do
Am 04.08.2008 um 10:58 schrieb Marcus Boerger:
Hello Lukas,
Monday, August 4, 2008, 10:49:43 AM, you wrote:
its not an edge optimization .. like i said its common practice in
many PHP frameworks. this way they can more easily develop the code,
while not having to suffer the drawbacks from a
On Mon, 4 Aug 2008, Marcus Boerger wrote:
Monday, August 4, 2008, 8:55:00 AM, you wrote:
Marcus Boerger wrote:
Hello Internals,
please let's not introduce new inconsistencies. Rather lets make
new stuff consistent with old stuff during the alpha phase of 5.3.
1) new keyword
Am 04.08.2008 um 10:42 schrieb Marcus Boerger:
Hello Dmitry,
Monday, August 4, 2008, 8:55:00 AM, you wrote:
Hi Marcus,
see below
Marcus Boerger wrote:
Hello Internals,
please let's not introduce new inconsistencies. Rather lets make
new
stuff consistent with old stuff during the
Hi,
On Sun, 2008-08-03 at 22:15 +0200, Pierre Joye wrote:
Hi Derick,
On Sun, Aug 3, 2008 at 6:34 PM, Derick Rethans [EMAIL PROTECTED] wrote:
you're not reading what I said. It does not make one single bit of sense
that a short function gives problems while an enormously long function
Christian,
On Mon, 2008-08-04 at 11:33 +0400, Dmitry Stogov wrote:
http://www.christian-seiler.de/temp/php/2008-07-24-reflection/reflection-closure-fixes-5.3.patch
http://www.christian-seiler.de/temp/php/2008-07-24-reflection/reflection-closure-fixes-6.patch
without applying and
On Mon, 2008-08-04 at 09:49 +0200, Hannes Magnusson wrote:
On Mon, Aug 4, 2008 at 01:29, Davey Shafik [EMAIL PROTECTED] wrote:
Hey,
it has come to my attention that stream_context_get_default()
is /grossly/ misnamed, considering
[...]
That doesn't really solve anything as the argument
Hello,
On Mon, Aug 4, 2008 at 12:51 PM, Etienne Kneuss [EMAIL PROTECTED] wrote:
But please check out the get_closure handler.
Scratch that, I didn't see the other mails ;)
Regards,
--
Etienne Kneuss
http://www.colder.ch
Men never do evil so completely and cheerfully as
when they do it
Hello,
Hello,
On Mon, Aug 4, 2008 at 6:57 AM, Stanislav Malyshev [EMAIL PROTECTED] wrote:
Hi!
1) I don't believe that having it thrown as another of those magic
method is a good idea. Rather, I'd like to have it represented by an
interface: Invokable. That way, type hints/checks can be done
On Mon, Aug 4, 2008 at 13:02, Johannes Schlüter [EMAIL PROTECTED] wrote:
On Mon, 2008-08-04 at 09:49 +0200, Hannes Magnusson wrote:
On Mon, Aug 4, 2008 at 01:29, Davey Shafik [EMAIL PROTECTED] wrote:
Hey,
it has come to my attention that stream_context_get_default()
is /grossly/
On Fri, 2008-08-01 at 14:11 +0400, Antony Dovgal wrote:
I mean completely no offense to the developers of these extensions, but
I would like them (extensions) to be thoroughly tested and mature first,
after that we can discuss the question of adding them to the core.
I think alpha stage is a
Marcus Boerger wrote:
Hello Dmitry,
Monday, August 4, 2008, 8:55:00 AM, you wrote:
Hi Marcus,
see below
Marcus Boerger wrote:
Hello Internals,
please let's not introduce new inconsistencies. Rather lets make new
stuff consistent with old stuff during the alpha phase of 5.3.
1)
2008/8/3 Marcus Boerger [EMAIL PROTECTED]:
Attached. I just naively moved some logic from __construct() into a
separate function and called it from both __construct() and
exchangeArray().
Well, naively or not, this seems about perfectly correct. Why don't you
simply apply this to HEAD and
hi,
On Mon, Aug 4, 2008 at 12:50 PM, Johannes Schlüter [EMAIL PROTECTED] wrote:
Correct PHP is supposed to work on all platforms therefore the code
has to work on Windows, too.
And now it does.
Now there are two questions Derick ask, which I see as valid questions:
a) Why does it break
Hello Andi,
please do not send auto replies to the list. Have a nice vacation anyway!
marcus
Monday, August 4, 2008, 11:35:22 AM, you wrote:
Hi,
I will be out of the office until Monday, August 11th on vacation with very
limited access to my emails.
Thanks,
Andi
Best regards,
Hi Christan,
Could you please look into this patch.
I'm not sure if explicit declaration of Closure::__invoke() is good
idea. As it cannot provide proper argument information.
May be the patch which you propose already solves this problem for
reflection. (I didn't have time to look into it).
Hi!
I'm not sure I understand what you mean? Either the interface covers
__invoke and $obj instanceof Invokable is a safe check to know if we
can $obj();, or it doesn't and we know nothing.
Well, if you put it this way, it's not going to work. However, I thought
there's middle ground - i.e.
Hi Dmitry, Hi Marcus,
I have no objections against ZE part of the patch.
If you like ext/reflection part please commit the whole patch.
Due to your cleanup wrt. handlers the reflection part will currently
(probably) segfault. I'll post an updated patch for this tomorrow.
Regards,
Christian
Hello,
On Mon, Aug 4, 2008 at 4:18 PM, Dmitry Stogov [EMAIL PROTECTED] wrote:
Hi Christan,
Could you please look into this patch.
I'm not sure if explicit declaration of Closure::__invoke() is good idea. As
it cannot provide proper argument information.
May be the patch which you propose
I'll see if I can write this as a patch instead; I was trying for
path of least resistance
Should be a fun exercise for me! Will get to it tonight.
- Davey
On Mon, Aug 4, 2008 at 7:14 AM, Hannes Magnusson
[EMAIL PROTECTED] wrote:
On Mon, Aug 4, 2008 at 13:02, Johannes Schlüter [EMAIL
Rasmus Lerdorf wrote:
Jani Taskinen wrote:
-- Changed PCRE, Reflection and SPL extensions to always be enabled.
(Marcus)
+- Changed PCRE, Reflection and SPL extensions to be always enabled.
(Marcus)
That was amazingly pedantic, even for you Jani. Captain Kirk blasted
away the split
Dmitry Stogov wrote:
I don't like multiple namespaces per file too.
As I remember they were introduced by Greg's request related to
ext/phar. May be he already changed his mind.
'package' or 'namespace' is not so important for me.
To be correct, this has nothing to do with ext/phar, but
Hi, I have a problem with socket_select(). I hope someone here can
point me in the right direction, because I'm stumped.
Basically, I'm getting this error:
Warning: socket_select() [function.socket-select]: no resource arrays
were passed to select in Net/Gearman/Client.php on line 197
Hannes Magnusson wrote:
On Mon, Aug 4, 2008 at 10:32, Lukas Kahwe Smith [EMAIL PROTECTED] wrote:
On 04.08.2008, at 10:28, Stefan Priebsch wrote:
Hannes Magnusson schrieb:
I don't think anyone but him likes multiple namespaces per file. I do
remember a PhD thesis sized mail from him
Hello Andi,
Monday, August 4, 2008, 5:29:33 PM, you wrote:
-Original Message-
From: Stefan Priebsch [mailto:[EMAIL PROTECTED]
Sent: Monday, August 04, 2008 1:29 AM
To: Hannes Magnusson
Cc: Dmitry Stogov; Marcus Boerger; internals@lists.php.net
Subject: Re: [PHP-DEV] Inconsistencies
/usr/local/src/php/php-5.3/ext/gd/gd.c: In function 'zif_imageloadfont':
/usr/local/src/php/php-5.3/ext/gd/gd.c:1607: warning: implicit declaration
of function 'overflow2'
/usr/local/src/php/php-5.3/ext/gd/gd.c: In function '_php_image_create_from':
/usr/local/src/php/php-5.3/ext/gd/gd.c:2586:
Em Ter, 2008-08-05 às 09:04 +1000, Sebastian Bergmann escreveu:
/usr/local/src/php/php-5.3/ext/gd/gd.c: In function 'zif_imageloadfont':
/usr/local/src/php/php-5.3/ext/gd/gd.c:1607: warning: implicit declaration
of function 'overflow2'
/usr/local/src/php/php-5.3/ext/gd/gd.c: In function
Ian Eure wrote:
I wrote a simple testcase that submits a single job to Gearman. If I run
it under Apache2, I get the socket_select() warning. If I run it from
the CLI, I don't. I'm also pointing the CLI at the Apache2 php.ini file.
At this point, I don't know how to track this any further. If
Greetings!
On 8/3/08 9:37 PM, Arnaud LB [EMAIL PROTECTED] wrote:
If sigaction is not available Zend Signal Handling will not be
enabled, so it will not be enabled on Windows (I assume sigaction is
not available on Windows, it is ?).
For pthreads and sigprocmask, tsrm_sigmask() can be improved
On Monday 04 August 2008 10:29:33 am Andi Gutmans wrote:
Re: braces, I don't think it's a big deal but I would prefer without
braces. Given that I think people should only have one namespace per file,
the braces is a PITA because it already starts you off in an additional
layer of
Marcus Boerger wrote:
Hello Lukas,
Monday, August 4, 2008, 10:49:43 AM, you wrote:
On 04.08.2008, at 10:41, Marcus Boerger wrote:
Hello Lukas,
Monday, August 4, 2008, 10:32:26 AM, you wrote:
On 04.08.2008, at 10:28, Stefan Priebsch wrote:
Hannes Magnusson schrieb:
I don't think
Dmitry Stogov wrote:
Marcus Boerger wrote:
Hello Dmitry,
Monday, August 4, 2008, 8:55:00 AM, you wrote:
Hi Marcus,
see below
Marcus Boerger wrote:
Hello Internals,
please let's not introduce new inconsistencies. Rather lets make new
stuff consistent with old stuff during the
50 matches
Mail list logo
