Hi Rasmus, On Thu, Mar 5, 2015 at 4:57 PM, Rasmus Lerdorf <ras...@lerdorf.com> wrote:
> On 03/04/2015 10:21 PM, Yasuo Ohgaki wrote: > > The same could be done for new names. > > Manual pages for localtime()/mktime()/etc would look a lot nicer. > > I hope there will be more favored developers with the RFC. Since I'm > > going to > > update manual to have alias search feature, developers used to POSIX can > > find > > PHP function name easily. If they would like to use POSIX name, they can > use > > it also. Nobody will try to remove POSIX names in the future, I suppose. > > > > In short, I would like to propose to have both PHP and IEEE names as > > officially > > valid names. Do you like this proposal? > > Nope, I don't. PHP is over 20 years old at this point and the PHP names > for the functions are one and the same as the IEEE names. I see > absolutely no reason to create a new class of "PHP" names. Since we have both violations, IEEE and PHP, having both would be possible resolution. I don't like to be somewhere between. Some functions confirm, but others don't, isn't nice to have. If we comply, complying as much as possible is better. IMHO. Anyway, if you would like to keep only mktime()/nl_langinfo()/etc without PHP coding standard names. I'll make this an option. What about adding IEEE confirmed aliases like isalpha()? Would you like to have these? Regards, -- Yasuo Ohgaki yohg...@ohgaki.net
