In a recent mail, some kind of issue regarding queryparams was
mentioned (Possibly related to namespaces). Could anybody explain what
the issue is, or point to where it's discussed?
On Mon, Jan 12, 2009 at 11:56 AM, Lukas Kahwe Smith m...@pooteeweet.org wrote:
- I guess we are not going to deal
On Tue, Jan 13, 2009 at 12:32 PM, troels knak-nielsen
troel...@gmail.com wrote:
In a recent mail, some kind of issue regarding queryparams was
mentioned (Possibly related to namespaces). Could anybody explain what
the issue is, or point to where it's discussed?
Currently, php replaces dots in
Am 13.01.2009 um 11:09 schrieb Alexey Zakhlestin:
On Tue, Jan 13, 2009 at 12:32 PM, troels knak-nielsen
troel...@gmail.com wrote:
In a recent mail, some kind of issue regarding queryparams was
mentioned (Possibly related to namespaces). Could anybody explain
what
the issue is, or point to
On Mon, 2009-01-12 at 15:03 +0100, Hannes Magnusson wrote:
On Mon, Jan 12, 2009 at 14:59, Lukas Kahwe Smith m...@pooteeweet.org wrote:
On 12.01.2009, at 14:56, Hannes Magnusson wrote:
Why did the LFS patch never get committed?
LFS = large file support?
AFAIK there is no patch to
On 13 Jan 2009, at 11:36, David Zülke wrote:
Am 13.01.2009 um 11:09 schrieb Alexey Zakhlestin:
On Tue, Jan 13, 2009 at 12:32 PM, troels knak-nielsen
troel...@gmail.com wrote:
In a recent mail, some kind of issue regarding queryparams was
mentioned (Possibly related to namespaces). Could
On 13 Jan 2009, at 11:09, Alexey Zakhlestin wrote:
On Tue, Jan 13, 2009 at 12:32 PM, troels knak-nielsen
troel...@gmail.com wrote:
In a recent mail, some kind of issue regarding queryparams was
mentioned (Possibly related to namespaces). Could anybody explain
what
the issue is, or point to
On Tue, 13 Jan 2009, Stefan Walk wrote:
On 13 Jan 2009, at 11:36, David Zülke wrote:
Am 13.01.2009 um 11:09 schrieb Alexey Zakhlestin:
On Tue, Jan 13, 2009 at 12:32 PM, troels knak-nielsen
troel...@gmail.com wrote:
In a recent mail, some kind of issue regarding queryparams was
this topic may be discussed before, but i'd bring it up again.
closure was introduced in PHP 5.3, function with its context can now
be stored in an callable object(or a handler in string type, whatever)
i think it's easy and read to introduce generator and yield operator
in php
let's see what
On 12.01.2009, at 23:04, Marcus Boerger wrote:
Hello Lukas,
it appears Dmitry and Stas are against that, so I let it for you to
decide whetehr you want me to drop all of it or continue workig on it
to make all I can ready for 5.3.0.
Just to clarify my role again. I am not the head decider.
Hello,
On Tue, Jan 13, 2009 at 1:30 PM, moo.tinys moo.ti...@gmail.com wrote:
this topic may be discussed before, but i'd bring it up again.
closure was introduced in PHP 5.3, function with its context can now
be stored in an callable object(or a handler in string type, whatever)
i think it's
Hi Andy,
All these tests are broken in an environment that defines a TZ variable,
you need to use date_default_timezone_set()
Can you fix these please.
Scott
andy wharmby wrote:
wharmby Tue Jan 13 13:38:20 2009 UTC
Added files: (Branch: PHP_5_3)
Hil Folks,
I hope this is the right place to ask for help. Talking to people on
#php on freenode convinced me that a developer's view might be required.
For a log of the discussion on irc look here:
http://spuerwerk.dyndns.org/~rfigura/php.fork-error.log
This is the little php program that
Hi list,
The following doesn't strike me as consistent behavior:
$a = new ArrayObject();
$a[foobar] = NULL;
echo (int) isset( $a[foobar] ); // Output: 1
While it's technically correct, I find it confusing. The reason is
probably because of a array_key_exists (or property_exists)
On Sun, 11 Jan 2009, Dmitry Stogov wrote:
Stanislav Malyshev wrote:
Derick Rethans wrote:
Not beyond running it from the test dir:
export ZEND_ALLOC=0
wget http://files.derickrethans.nl/test.tar.gz
tar -xvzf test.tar.gz
cd test
#php-5.2dev test.php
php test.php
echos:
Hello,
On Tue, Jan 13, 2009 at 4:43 PM, Mark van der Velden m...@dynom.nl wrote:
Hi list,
The following doesn't strike me as consistent behavior:
$a = new ArrayObject();
$a[foobar] = NULL;
echo (int) isset( $a[foobar] ); // Output: 1
While it's technically correct, I find it
On 1/13/09 4:09 AM, Alexey Zakhlestin wrote:
In 6.0, on the other hand, register_globals is not available. So, it
doesn't make sense to have replacement there too.
5.3 is left with status-quo:
?a.b.c=10 = $a_b_c, $_GET['a_b_c']
6.0 will have:
?a.b.c=10 = $_GET['a.b.c']
What about the
Hello,
On Tue, Jan 13, 2009 at 12:07 AM, Stanislav Malyshev s...@zend.com wrote:
Hi!
1) a non static closure assigned to an instance changes the closures
this to be set to the actual object:
I'm not sure why would you expect this. If you have closure that has some
bound $var inside, and
Hello Stanislav,
Tuesday, January 13, 2009, 12:07:31 AM, you wrote:
Hi!
1) a non static closure assigned to an instance changes the closures
this to be set to the actual object:
I'm not sure why would you expect this. If you have closure that has
some bound $var inside, and you use it in
Hello Stanislav,
Monday, January 12, 2009, 11:19:51 PM, you wrote:
Hi!
it appears Dmitry and Stas are against that, so I let it for you to
decide whetehr you want me to drop all of it or continue workig on it
to make all I can ready for 5.3.0.
I'm not precisely against it because I'm
Hi!
Also, this adds very new thing to PHP - objects that change while being
assigned. I am not sure it is a good thing.
Well Closures are a brand new thing in PHP. So far we had nothing even
remotely close to the closures we have right now.
There are a lot of different features in PHP,
On the contrary, It will most likely require a lot of changes to
provide structures that are able to store their execution context to
be able to resume it later. I.e.
function foo() {
error_reporting(0);
yield foo;
trigger_error(foo, E_NOTICE);
yield bar;
}
$e = false;
just a note about it
in javascript, this ($this in php) is a special variable in closure,
this is always bound to the object of object.method(...) when it
is called, whenever i want a this of closure creation time context,
i use:
var _this = this;
return function() { _this.prop = 123;
22 matches
Mail list logo
