HI all,
On Fri, Jan 3, 2014 at 2:49 AM, Robert Parker <[email protected]> wrote:
> I would consider myself one of those php developers. I know very little c,
> and java. Javascript is my second language after php. Most php developers
> have yet to move towards 5.3 and don't know how to even use namespaces or
> what they are. They often use wordpress or drupal which are very slow to
> adapt.
>
> Considering how slow and hard it is for most php developers to migrate to
> new versions of php I do not think creating aliases or changing the names
> would be beneficial. Different developers would use different aliases and
> it would confuse a lot of php developers.
>
This proposal does not intend to force users to adopt new names, but ensure
PHP popularity in the long run.
Are new users willing to learn language that have full of inconsistent
names
even for basic/standard/default functions?
My intention to have consistent function names for old function is
- to ensure PHP as attractive language to learn even 10 or 20 years later.
I agree that adoption of new feature is slow. If we made function names
consistent now, there would be codes around uses historic names 10 years
later, but it does not matter for the purpose of this proposal.
De facto Standard names such as strchr() would be acceptable names even
20 years from now. Other functions such as GD functions are better to have
consistent names.
Please consider this proposal is for new users that will learn PHP from now
or
in the future.
Regards,
--
Yasuo Ohgaki
[email protected]