Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I agree with the idea, but there's room for a coordinated effort nonetheless. From a naming consistency standpoint on strpos vs str_replace, for example, we could have a new set of function names aliased to the old, and let those run in parallel for a while, with deprecation notices on use of the old ones. Ugly? Perhaps, but it's a way forward to standardize the internal function naming without breaking BC overnight.


The PHP team does this already ... it is a slow process, but I think in the right direction: http://php.net/manual/en/migration53.deprecated.php


Not quite for the same reasons it seems. But, since they already do do this, why not take on standardizing function spacing? strpos would become str_pos, etc.


Because there just isn't that much value in it.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: