# php54 vote

- Thread: https://externals.io/message/55744
- Original archive: https://news-web.php.net/php.internals/55744
- Started by Ferenc Kovacs on 2011-10-08T01:07:43+00:00
- Messages: 6
- Reply by email to internals@lists.php.net
- More for agents: search with https://externals.io/search.md?q={query} · JSON API at https://externals.io/api · documentation at https://externals.io/llms.txt

---

## #55744 — Ferenc Kovacs — 2011-10-08T01:07:43+00:00

URL: https://externals.io/message/55744#55744

Hi

https://wiki.php.net/todo/php54/vote
I've just noticed that the php namespace and the primitive types
(string, bool, int) are still not reserved.
the primitive types didn't had the 66% of the votes, but the php
namespace did, so at least that should have been reserved in 5.4
already.
what is the status about that?

-- 
Ferenc Kovács
@Tyr43l - http://tyrael.hu

---

## #55751 — Patrick ALLAERT — 2011-10-08T14:02:36+00:00

URL: https://externals.io/message/55744#55751 · In reply to: #55744

2011/10/8 Ferenc Kovacs <tyra3l@gmail.com>:
> Hi
>
> https://wiki.php.net/todo/php54/vote
> I've just noticed that the php namespace and the primitive types
> (string, bool, int) are still not reserved.
> the primitive types didn't had the 66% of the votes, but the php
> namespace did, so at least that should have been reserved in 5.4
> already.
> what is the status about that?

As far as I remember the thread about that, we concluded that while it
may be ok to make them reserved words in the global namespace, it is
absolutely not reasonable to make them reserved in a way it would
prevent creating namespaced classes like: \Company\Types\Int,
\Company\Types\String.
Namespaces being created, among other reasons, to avoid name
collisions, it would be unacceptable to have that BC break for people
having take care of namespacing that kind of classes.
And since the parser is too dumb for now, we just can't make it (cfr
your own mail in that thread).

The votes made on that topic where mostly done by people who obviously
haven't take care of the technical limitations nor having followed the
BC problems it generates.
That topic shouldn't have been voted at all.

Ref: http://marc.info/?t=131031633300001

Cheers,
Patrick

---

## #55754 — Pierre Joye — 2011-10-08T15:12:13+00:00

URL: https://externals.io/message/55744#55754 · In reply to: #55751

> The votes made on that topic where mostly done by people who obviously
> haven't take care of the technical limitations nor having followed the
> BC problems it generates.
> That topic shouldn't have been voted at all.

It was voted on the idea given that the tech issues and BC were
solved, and that's a requirement for any RFC to be accepted.


-- 
Pierre

@pierrejoye | http://blog.thepimp.net | http://www.libgd.org

---

## #55757 — Stas Malyshev — 2011-10-08T17:50:53+00:00

URL: https://externals.io/message/55744#55757 · In reply to: #55744

Hi!


> I've just noticed that the php namespace and the primitive types
> (string, bool, int) are still not reserved.

Reserving primitive types was decided not to be practically 
implementable. As for reserving namespace PHP, this was supposed to be 
documentation thing and it will be added to the manual.

-- 
Stanislav Malyshev, Software Architect
SugarCRM: http://www.sugarcrm.com/
(408)454-6900 ext. 227

---

## #55759 — Ferenc Kovacs — 2011-10-09T05:32:26+00:00

URL: https://externals.io/message/55744#55759 · In reply to: #55751

thanks for the heads up, I didn't remembered that thread :(
btw. didn't we had some parser improvement patch laying around for a while now?


> 2011/10/8 Ferenc Kovacs <tyra3l@gmail.com>:
> > […]
>
> As far as I remember the thread about that, we concluded that while it
> may be ok to make them reserved words in the global namespace, it is
> absolutely not reasonable to make them reserved in a way it would
> prevent creating namespaced classes like: \Company\Types\Int,
> \Company\Types\String.
> Namespaces being created, among other reasons, to avoid name
> collisions, it would be unacceptable to have that BC break for people
> having take care of namespacing that kind of classes.
> And since the parser is too dumb for now, we just can't make it (cfr
> your own mail in that thread).
>
> The votes made on that topic where mostly done by people who obviously
> haven't take care of the technical limitations nor having followed the
> BC problems it generates.
> That topic shouldn't have been voted at all.
>
> Ref: http://marc.info/?t=131031633300001
>
> Cheers,
> Patrick
>



-- 
Ferenc Kovács
@Tyr43l - http://tyrael.hu

---

## #55760 — Ferenc Kovacs — 2011-10-09T05:34:57+00:00

URL: https://externals.io/message/55744#55760 · In reply to: #55757

> Hi!
>
> 
> > […]
>
> Reserving primitive types was decided not to be practically implementable.
> As for reserving namespace PHP, this was supposed to be documentation thing
> and it will be added to the manual.
>

thanks for clarifying.
-- 
Ferenc Kovács
@Tyr43l - http://tyrael.hu
