2015-03-05 22:20 GMT+02:00 Yasuo Ohgaki <yohg...@ohgaki.net>: > Hi Arvids, > > On Thu, Mar 5, 2015 at 9:32 PM, Arvids Godjuks <arvids.godj...@gmail.com> > wrote: > >> 2015-03-05 13:49 GMT+02:00 Pierre Joye <pierre....@gmail.com>: >> > >> > >> > I will say it again a last time, in my opinion only a clean API; >> > object-like or real object as long as performance is not affected is >> > the only way I could see to actually solve this problem. >> > >> > Changing the names, argument order (pointless once we will have named >> > arguments, btw) and similar solutions are band aids solutions, >> > confusing at best, terrible at worst. It is pointless to do it after >> > almost two decades for some of them. >> > >> > -- >> > Pierre >> > >> > I'm with Pierre here. >> Adding aliases is gonna mess up things even more. For example - >> autocomplete will become hard to navigate. It's already quite lengthy list >> a lot of the times and it's easier just to write the whole function name >> sometimes by hand. Adding aliases will make it worse. >> > > I agree. Therefore, I'm going to update manual also so that it recommends > main function, not aliases. Aliases should be alternative. > > Manual and IDE don't have to list all of them. New manual lists only main > functions, does not have dedicated pages for aliases but aliases are > mentioned > in main function page as aliases. > > >> >> We really need a new API, that is not crossing paths with the old. That >> way >> people can start building stuff on new API's and we could phase out the >> old >> mess, for example: depricate in PHP8, remove in PHP9. >> Stop-gap measures have created enough problems already, or did everyone >> suddenly got an amnesia and forgot all the past lessons on the list? > > > PHP should be multi paradigm language, not pure OO language. > IMO. Python does good job. > > "Python is a multi-paradigm programming language: object-oriented > programming > and structured programming are fully supported, and there are a number of > language features which support functional programming and aspect-oriented > programming" > http://en.wikipedia.org/wiki/Python_%28programming_language%29 > > It sounds like there are people who would like to discard procedural APIs. > PHP has born as procedural language. It will not happen in short term at > least. We are far from having rich and good enough OO APIs sets to make > PHP a pure OO languages. > > This leads to conclusion that we need to maintain/improve procedural APIs > even if we are going to make PHP a pure OO language. > > I finally understand why some of us against this change and suggest OO APIs > as alternative. It's reasonable making procedural APIs a > legacy/unmaintained/ > messed up to discard procedural APIs someday. I'm against it. PHP should > be like Python in this regard. IMO. > > Regards, > > -- > Yasuo Ohgaki > yohg...@ohgaki.net >
Why not take advantage of namespaces and do the new API, building it up version by version (sure it can't be done in one go), so probably the extensions gonna follow too. That allows you to use as OO interface, so do the functions. Well, yes, it will be under a namespace, but at least new projects can be started that way. And old code will be easy enough to port, it's mostly a question of refactoring tools. Aliasing is a stop-gap measure, isn't it? API's tend to get redesigned and PHP's is due to a major makeover. So, why not embrace it? No one's forcing to retire the old one any time soo, and I belive people understand it will be a very long time before it is phased out, if ever (well, I think in like 20 years probably is doable). And if done right, it may be done in a way that if you don't need it, you can leave out the old API on compile stage - not sure if doable thought. Arvids.
