Hi Stas:
> Nobody runs PHP with -n, who would you do that? INIs are the
> recommended setting, if you ignore that, you do it at your own
> peril.
I've seen many servers that run with php.ini files that have only a few
lines in them, relying on the defaults for most of the behavior.
--Dan
--
T
On 16/07/11 16:12, David Soria Parra wrote:
Hi Internals,
Hi David,
just a heads up on the proposed "make primitives types reserved words"
change. the current votes are 36 to 21 in favor of implementing it.
This change has a big impact on backward compatibility and will break
existing cod
even more than vote, we can veto it due to a huge BC break (use of
primitive names inside a namespace, f.e.)
On Sat, Jul 16, 2011 at 4:12 PM, David Soria Parra wrote:
> Hi Internals,
>
> just a heads up on the proposed "make primitives types reserved words"
> change. the current votes are 36 to
Hi Internals,
just a heads up on the proposed "make primitives types reserved words"
change. the current votes are 36 to 21 in favor of implementing it.
This change has a big impact on backward compatibility and will break
existing code. Possible work arounds as discussed on the mailinglist
have
I'm not familiar with the internal implementation of GC in PHP but if
the current garbage collection implementation makes catching the gc
event non-trivial I'd agree and vote for postponing my "SplQueue
ref_queue" suggestion until the future. It could always be added later
and there is the temporar
On Sat, Jul 16, 2011 at 1:13 PM, Hannes Landeholm wrote:
> Since Weak references is already an established concept in many OOP
> languages a lot can be learned from their implementation. A lot of the
> potential related problems and solutions has already been studied.
> Anyone who wish to contribu
Since Weak references is already an established concept in many OOP
languages a lot can be learned from their implementation. A lot of the
potential related problems and solutions has already been studied.
Anyone who wish to contribute to this feature should start by reading
this excellent article
On Sat, Jul 16, 2011 at 12:11 PM, Hannes Landeholm wrote:
> I was going to add some content to
> https://wiki.php.net/rfc/weakreferencesnow but the wiki tells me that
> the page is read only for me. I couldn't find
> any details on who to contact to change this.
>
> ~Hannes
>
I already asked bjor
On Sat, Jul 16, 2011 at 12:14 PM, Richard Quadling wrote:
> On 14 July 2011 20:42, Ferenc Kovacs wrote:
>> To spare the "5.4 features vote" thread from the off-topic discussion,
>> we can continue here.
>> Hannes Landeholm brought this idea up, see
>> http://news.php.net/php.internals/53956 and
>
On 14 July 2011 20:42, Ferenc Kovacs wrote:
> To spare the "5.4 features vote" thread from the off-topic discussion,
> we can continue here.
> Hannes Landeholm brought this idea up, see
> http://news.php.net/php.internals/53956 and
> http://news.php.net/php.internals/53959
> I would suggest that H
I was going to add some content to
https://wiki.php.net/rfc/weakreferencesnow but the wiki tells me that
the page is read only for me. I couldn't find
any details on who to contact to change this.
~Hannes
Hello,
I just realized you could actually utilize the __destruct method to catch
the event I described in my last post. The SplWeakRef class as currently
defined in the RFC would therefore suffice to build a userland class that
automatically garbage collects indexes.
~Hannes
12 matches
Mail list logo
