>
> > 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.
>
> 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
>
> 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
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
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
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
