Hello there,
I don't have enough time to write more detailed example, but I still want to
write my opinion.
I totally agree with Stanislav, because for me magic functions should be
used in last leaf of some class extend tree. They are some kind of feature
when you are producing the non-framework,
Hi,
After some discussion with Dmitry, he and I have continued to improve
the current closure patch. You can find the current proposal with
patches for 5_3 and HEAD here:
http://wiki.php.net/rfc/closures
(Please read it again, I've changed quite a lot.)
Basically, it's the syntax with use ($le
Hi,
I'd like to fix the resolution order of Countable::count() vs
count_elements handler.
Currently, things are done like this:
1) check if the object implements countable, if so, call it's method
2) if not, check if count_elements handler is defined, if so, use it.
This is a problematic order o
On Tue, Jul 01, 2008 at 05:55:49PM -0500, Ralph Schindler wrote:
> In PHP 5.3 snaps, it appears that magic methods __isset, __unset, __get,
> __set must have a public visibility or the engine will trigger a
> warning. Why is this? It works as expected in 5.x branches.
Because that's what the
Hi!
Re-reading the proposal, I encountered something unexpected:
$replacer = $example->getReplacer ('goodbye');
echo $replacer ('hello world'); // goodbye world
$replacer->setSearch ('world');
echo $replacer ('hello world'); // hello goodbye
Does it mean closure would forward all method calls t
Hi Stanislav,
Or did you just mean $example->setSearch() and I'm worried about
nothing? :)
Yes, absolutely, Sorry for the confusion caused. ;-)
I fixed that in the Wiki.
In this case, I'd just propose to have getThis() anyway.
I don't see a need, but I'm not against it. Should be extremel
On 26.06.2008, at 10:46, Bijl, Gomar wrote:
Hi
We have a problem with the (ODBC) persistent database connection. We
have found that every PHP-session, using the same dsn, user and
password, are getting the same persistent connection by a reasonable
chance.
Also meaning that if a database trans
Aloha,
Since Johannes has been stumped (and therefore not as visible as he
would have hoped) with work and 5.3 CVS is already filled brim with
awesome new features, I have been approached by several people
wondering how we can speed up the process. I have always said I am
available to pla
I think the sooner we set on 5.3 release path, the better of we will
be. As a past RM I can tell you that the more new features exist in a
release, the more challenging the release process is. If a faster
release cycle means having 2 RMs, then we have 2 RMs, thats my opinion
anyhow.
On 2-
On 02.07.2008, at 13:41, Christian Seiler wrote:
I've spoken to Dmitry and he said the patch will be committed to HEAD
soon. Since both Dmitry and I still want to have it in 5_3 too, we'd
want to ask for opinions on this again - especially since after
quite a
lot of thorough review and discu
On Wed, Jul 2, 2008 at 22:00, Lukas Kahwe Smith <[EMAIL PROTECTED]> wrote:
> @Philipp: Since you are the god of documentation .. How are things looking
> on the scratchpad [8] you started?
Philip, one p, recently moved to Nicaragua (last weekend actually) and
isn't really "available" these days :)
On Wed, 2008-07-02 at 22:24 +0200, "Hannes Magnusson" wrote:
> On Wed, Jul 2, 2008 at 22:00, Lukas Kahwe Smith <[EMAIL PROTECTED]> wrote:
> > @Philipp: Since you are the god of documentation .. How are things looking
> > on the scratchpad [8] you started?
>
> Philip, one p, recently moved to Nicar
On Wed, Jul 2, 2008 at 22:00, Lukas Kahwe Smith <[EMAIL PROTECTED]> wrote:
> Summary:
> Everybody review [1] and make sure all items you care about are on the list
> and your name only appears next to stuff you are actually able to complete
> in a timely manner.
..One more thing: My GSoC student,
Folks:
On Wed, Jul 02, 2008 at 10:24:25PM +0200, Hannes Magnusson wrote:
> functions/features now throwing E_DEPRECATED) is missing...
I just added the E_DEPRECATED constant to errorfunc.constants.php. Now
we need to make sure that each function that error has been applied to
has it's manual p
Hi,
On Wed, Jul 2, 2008 at 10:00 PM, Lukas Kahwe Smith <[EMAIL PROTECTED]> wrote:
> Aloha,
>
> Since Johannes has been stumped (and therefore not as visible as he would
> have hoped) with work and 5.3 CVS is already filled brim with awesome new
> features, I have been approached by several people
Hi!
1) intl extension
Last discussion ended without a decision on the class naming [10]. I
specifically remember Derick taking issue with intl ext "invading" the
date ext namespace. Stas however arguing that the intl ext is supposed
to bring some forwards compatibility to PHP 6 and therefore
On 2 Jul 2008, at 14:38, Johannes Schlüter wrote:
On Wed, 2008-07-02 at 22:24 +0200, "Hannes Magnusson" wrote:
On Wed, Jul 2, 2008 at 22:00, Lukas Kahwe Smith
<[EMAIL PROTECTED]> wrote:
@Philipp: Since you are the god of documentation .. How are things
looking
on the scratchpad [8] you sta
Lukas Kahwe Smith wrote:
Aloha,
Since Johannes has been stumped (and therefore not as visible as he
would have hoped) with work and 5.3 CVS is already filled brim with
awesome new features, I have been approached by several people
wondering how we can speed up the process. I have always said
On Wednesday 02 July 2008 6:41:20 am Christian Seiler wrote:
> Hi,
>
> After some discussion with Dmitry, he and I have continued to improve
> the current closure patch. You can find the current proposal with
> patches for 5_3 and HEAD here:
>
> http://wiki.php.net/rfc/closures
>
> (Please read it
On 03.07.2008, at 02:04, Philip Olson wrote:
Essentially the plan is to DocBookify it once 5.3 nears release but
today that page requires additional content. Random people add
content randomly and unfortunately I'm no longer able to lead this
effort so please take over the task of 5.3 upgr
On 03.07.2008, at 02:08, Alan Knowles wrote:
Lukas Kahwe Smith wrote:
Aloha,
Since Johannes has been stumped (and therefore not as visible as he
would have hoped) with work and 5.3 CVS is already filled brim with
awesome new features, I have been approached by several people
wondering h
21 matches
Mail list logo