On Fri, Jan 25, 2013 at 2:04 PM, Rasmus Lerdorf <ras...@lerdorf.com> wrote:
> On 01/25/2013 10:55 AM, Seva Lapsha wrote: > > Well, how about renaming the functions, create aliases for BC and throw > > E_DEPRECATED or E_STRICT on their usage? And write a PEAR script bundled > > with the distribution to migrate to the new convention? > > Throwing warnings on perfectly working code is really a bad idea. It could be a new type of notice then, which could be controlled by configuration. > It annoys users, The configuration could be turned off by default. > slows down their code, Isn't it a flaw of the current implementation of throwing messages, which could be improved? AFAIU, if suppressed warnings would not be processed as the active ones, the performance effect would be negligible to zero. > and doesn't add any value at all to them. > It would add the value to those who care. > It should also be noted that many of the function names that people > don't think are consistent are actually quite consistent when you > consider that PHP is just a thin wrapper on top of underlying libraries. > Functions from libc like tempnam() and strlen() are perfectly fine. The > fact that you can go to your Linux command line and type: "man tempnam" > to get a good idea of what is happening behind the scenes of the PHP > function of the same name is a good thing. > True. Don't get me wrong, I personally don't mind using the good old names, even typos in the names have their own charm. I just think that the point of view of order-freaks could be respected a little after all these years of complaints, so I'm trying to find a compromise and more PHP users would be happy. :) > > -Rasmus > >
