Re: [PHP-DEV] Ten years estimated Plan to replace PHP’s inconsistent API

2015-03-23 Thread Nathan wesley
> > > i didn't mention any break or things. also many languages are different > > Yes you did. You just proposed removing large part of PHP API. That > would break things, there can be no confusion about it. I just agree with you. we shouldn't :) the old API will stay no one will ever remove it.

Re: [PHP-DEV] Ten years estimated Plan to replace PHP’s inconsistent API

2015-03-23 Thread Stanislav Malyshev
Hi! > famous articles written about it like "PHP fractal of bad design" and That article. Which is from what I remember last time reading it was about 75% like "why I need to look in the manual instead of language being magically exactly the way I imagine it should be without any basis?". And ano

Re: [PHP-DEV] Ten years estimated Plan to replace PHP’s inconsistent API

2015-03-23 Thread Nathan wesley
> > Hi! > > > This makes an opportunity to replace the old API with object oriented one > > preventing any kind of BC break. > > > > But instead of using this as an extension because of some limitations > like > > “string”->startsWith(‘s’); the API should be bundled with the engine (not > > written

Re: [PHP-DEV] Ten years estimated Plan to replace PHP’s inconsistent API

2015-03-22 Thread Stanislav Malyshev
Hi! > This makes an opportunity to replace the old API with object oriented one > preventing any kind of BC break. > > But instead of using this as an extension because of some limitations like > “string”->startsWith(‘s’); the API should be bundled with the engine (not > written in PHP). This is

Re: [PHP-DEV] Ten years estimated Plan to replace PHP’s inconsistent API

2015-03-22 Thread Yasuo Ohgaki
Hi Nathan, On Sat, Mar 21, 2015 at 1:01 PM, Nathan wesley wrote: > I know that many people talked about this over and over. > > Why it’s not possible to change the old PHP API ? > > The answer is always because it will make HUGE BC breaks > > I’ve seen this wonderful idea about scalar object

RE: [PHP-DEV] Ten years estimated Plan to replace PHP’s inconsistent API

2015-03-22 Thread François Laupretre
>De : Nathan wesley [mailto:nathan.o.wes...@gmail.com] > > if you're going to write API for string manipulation for example you want it > either Object Oriented or procedural style. > because the API should be fluent method chaining etc. you don't want to stop > the chain and wrap it with a fu

Re: [PHP-DEV] Ten years estimated Plan to replace PHP’s inconsistent API

2015-03-21 Thread Nathan wesley
> > I think that, while attractive, using the same syntax for object methods > and scalar 'pseudo-'methods is too ambiguous. We just need to solve two > issues : intuitive order of arguments and nested call readability. We don't > need to implement the whole OO stuff for scalars. Except this detail

Re: [PHP-DEV] Ten years estimated Plan to replace PHP’s inconsistent API

2015-03-21 Thread Nathan wesley
This shouldn't be for PHP 7.0 ofcourse it's too late. it takes a lot of work and we don't want to get it wrong the second time :) but in any release before PHP 8 On Sat, Mar 21, 2015 at 10:25 AM, Pierre Joye wrote: > > On Mar 21, 2015 2:15 PM, "Levi Morrison" wrote: > > > > > I know that many

Re: [PHP-DEV] Ten years estimated Plan to replace PHP’s inconsistent API

2015-03-21 Thread Nathan wesley
How you don't think this is so important ? i stated this because it's so predictable that someone will say it. Firstly why it's "fake" ? i prefer "elegant" maybe not the PERFECT solution ? i suggest that you compare the two choices. and what would you chose if you're a new comer. Secondly this is

RE: [PHP-DEV] Ten years estimated Plan to replace PHP’s inconsistent API

2015-03-21 Thread François Laupretre
> De : Nathan wesley [mailto:nathan.o.wes...@gmail.com] > > The old API should be deprecated in PHP 8.0 and removed completely in PHP > 9.0 (finally) That's totally unrealistic. The old API will remain forever (well, we'll examine the case again in 20 years...). I had planned to propose somethi

Re: [PHP-DEV] Ten years estimated Plan to replace PHP’s inconsistent API

2015-03-21 Thread Lester Caine
On 21/03/15 04:01, Nathan wesley wrote: > The old API should be deprecated in PHP 8.0 and removed completely in PHP > 9.0 (finally) WHY? You don't HAVE to use the current API and wiping out all of the legacy code does not seem like a 'gain'. The two can co exist. > I hope that you take this serio

Re: [PHP-DEV] Ten years estimated Plan to replace PHP’s inconsistent API

2015-03-21 Thread Niklas Keller
2015-03-21 8:25 GMT+01:00 Pierre Joye : > On Mar 21, 2015 2:15 PM, "Levi Morrison" wrote: > > > > > I know that many people here will say that it’s not that important > > > developers get used to this API and many tutorials based on it. > > > > As you guessed, I don't think this is so important t

Re: [PHP-DEV] Ten years estimated Plan to replace PHP’s inconsistent API

2015-03-21 Thread Pierre Joye
On Mar 21, 2015 2:15 PM, "Levi Morrison" wrote: > > > I know that many people here will say that it’s not that important > > developers get used to this API and many tutorials based on it. > > As you guessed, I don't think this is so important that we should > create a new "fake" object syntax for

Re: [PHP-DEV] Ten years estimated Plan to replace PHP’s inconsistent API

2015-03-21 Thread Levi Morrison
> I know that many people here will say that it’s not that important > developers get used to this API and many tutorials based on it. As you guessed, I don't think this is so important that we should create a new "fake" object syntax for scalar. That's shooting a mouse with an elephant gun. -- P

[PHP-DEV] Ten years estimated Plan to replace PHP’s inconsistent API

2015-03-20 Thread Nathan wesley
I know that many people talked about this over and over. Why it’s not possible to change the old PHP API ? The answer is always because it will make HUGE BC breaks I’ve seen this wonderful idea about scalar objects authored by nikic github https://github.com/nikic/scalar_objects. This will