Hello Dmitry,
can't we just commit it and when sombody finds a better working keyword we
change it? (I'd like to use this in SPL_Types, to precise my reasoning).
regards
marcus
Friday, March 31, 2006, 8:47:42 AM, you wrote:
> Hi Michael,
>> -Original Message-
>> From: Michael Livel
I still have some questions into Dmitry re: the patch before I feel
comfortable with applying it.
The better keyword is this::. I want to use that for now and not
static:: which says nothing about what this is. When I brougth it up
many ppl liked it.
Andi
At 06:41 AM 3/31/2006, Marcus Boerg
Hi Marcus,
I don't like to commit it as is.
The problem that this seldom-used feature will slowdown each PHP call.
I'll measure performance lose on next week.
Please, test this patch too.
I might forget some edge cases.
Thanks. Dmitry.
> -Original Message-
> From: Marcus Boerger [mail
Hello folks,
I'm the original author of the gd graphics library used in PHP.
Although there are alternatives, gd is probably the most common way to
manipulate images on the fly in PHP code.
As some of you are no doubt aware, I haven't released a new gd update
in quite some time. Other projects
Translating the documentation
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
1. Interest. Does the PHP community want to take this on? PHP developers,
including some involved with patching the PHP "fork" of gd, have
expressed interest in the past. But I'm not assuming they are
still interested. So, you tell me.
Yes, we are definitely still very interested in gd. We woul
On Tue, 28 Mar 2006 16:35:24 -0600 (CST)
[EMAIL PROTECTED] (Thomas Boutell) wrote:
> Hello folks,
>
> I'm the original author of the gd graphics library used in PHP.
> Although there are alternatives, gd is probably the most common way
> to manipulate images on the fly in PHP code.
>
> As some o
I ran the following code on 5.0.4 and 5.1.0 with identical results...
Could someone shed light one whether the observed behaviour is
intentional and/or correct?
I expected that one of the following would occur (which obviously doesn't :-):
1. the line commented with 'SET 2' would trigger a
call
Pierre wrote:
> I'm obviously volunteer to lead the project if there is a need for one...
IMHO there _is_ a need for a lead, and I can't imagine anyone but you doing
it if Mr. Boutell cannot. Thanks for volunteering, and thanks to Mr. Boutell
for a fine product that will continue to flourish at
The __set() method is called when a property of a class is set, __get()
when a property is retrieved.
An array is simple a way of listing things; the array itself is a piece
of data. When you set a key in that array, you are not setting the
array. It may help to think of it like this:
$t =
10 matches
Mail list logo
