Yes, it's extremely useful, especially because most of the php developers are developing under Linux and most of them are coming from C and many other languages. Give ma a break... Second thing, we're afraid of throwing deprecated errors. Let's see the case. On production machines there are errors hidden from the users (display errors: none or just strict, notice, deprecated types hidden), experienced developers when they will not like them during development will disable them or migrate their code, new developers will just learn new API. Where is the problem? I'm not talking about removing some functions but just deprecating them to to get some time and simply to be ready to improve the PHP as a language in the future when time will come. 25 sty 2013 20:04, "Rasmus Lerdorf" <ras...@lerdorf.com> napisał(a):
> 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 > annoys users, slows down their code, and doesn't add any value at all to > them. > > 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. > > -Rasmus > >
