That is what I will do.
What has become clear to me is that this feature does indeed have a lot
of promise, and me working on it further to address new concerns (and
directions) would not be wasted time.
I will close the vote, clean up the patch to address new concerns, then
bring this back
I somewhat agree; using __CLASS__ would make it more obvious that it's
compile-time rather than runtime, IMO.
It's not always going to be compile-time.
For self::class and Foo::class, it will be compile time every time. For
static:class and parent::class, that has to be done at runtime as
Is it safe to write PHP extensions in C++?
I read on Sara Golemon's book that the zend engine can bailout on a request
during a call to php_error_docref() or even an emaloc() that exceeds the
allowed memory, doing an immediate longjmp() to the shutdown part of the
engine.
longjmp() does not wor
hi Ferenc,
Can you put that in the wiki too instead? So it can be clarified there
directly if necessary.
Thanks,
On Fri, Sep 14, 2012 at 11:36 AM, Ferenc Kovacs wrote:
> Hi,
>
> I was asked in a private email that it is true or not that *anybody* can
> create an RFC.
> As this isn't the first t
On Fri, Sep 14, 2012 at 10:55 AM, Derick Rethans wrote:
> On Thu, 13 Sep 2012, Daniel Brown wrote:
>
> > On Thu, Sep 13, 2012 at 3:21 PM, Stas Malyshev
> wrote:
> > > Hi!
> > >
> > > Does anybody know who is responsible the snaps.php.net machine? It
> seems
> > > to be serving 5.4 builds under t
Hi,
I was asked in a private email that it is true or not that *anybody* can
create an RFC.
As this isn't the first time to see that question I think that we could
document that a little bit clearly.
Here is how I responded to the question, and maybe we could improve on it
and put that somewhere i
In general it'll work, but it'll waste memory.
Thanks. Dmitry.
On 09/14/2012 12:33 PM, Patrick Schaaf wrote:
Hi,
if it looks, smells, and works like a class constant, can't just BE a
class constant, automatically created, but just as-if "const class =
'xxx';" had been present in the definition
On Thu, 13 Sep 2012, Daniel Brown wrote:
> On Thu, Sep 13, 2012 at 3:21 PM, Stas Malyshev wrote:
> > Hi!
> >
> > Does anybody know who is responsible the snaps.php.net machine? It seems
> > to be serving 5.4 builds under then name of php-trunk and that confuses
> > people. Not only we don't have
Hi,
if it looks, smells, and works like a class constant, can't just BE a class
constant, automatically created, but just as-if "const class = 'xxx';" had
been present in the definition in the first place?
Not that I know php code internals in any thorough way, but I imagine that
that approach wo
Patrick ALLAERT wrote:
> 2012/9/14 Dmitry Stogov :
>> Finally, may be SOMETHING::__CLASS__ is a bit more clear than
>> SOMETHING::class.
>
> That is the reason why I voted "no", but more because of the token
> used than the feature.
> I previously stated that I preferred __CLASS__ as well to be mo
2012/9/14 Dmitry Stogov :
> Finally, may be SOMETHING::__CLASS__ is a bit more clear than
> SOMETHING::class.
That is the reason why I voted "no", but more because of the token
used than the feature.
I previously stated that I preferred __CLASS__ as well to be more in
line with what we currently h
Hi Ralph,
You persuade me. :)
The SOMETHING::class syntax looked wired to me because I didn't
understand it.
However, the SOMETHING::class syntax might be considered as a reference
to a predefined class constant and in this case it looks quite
consistent. I suggest to reflect it in RFC and
12 matches
Mail list logo
