> On 25 May 2015, at 18:40, Jakub Zelenka <bu...@php.net> wrote: > >> Anyway, as I told in a previous thread, while approach of this rfc solves >> immediate problem, it is not future-proof flexible and exposing low-level >> type based parsing is a better idea >> > IIRC your initial proposal was about converting everything to objects which > is not flexible at all as it suffers exactly from the same problems as this > RFC. The only difference is using object instead of string. I think that the > above is much more flexible... > > However as I said before it is quite a big feature that could be done only in > the minor version and requires considerably more time for implementation.
The difference is, that object would preserve type information from the document. Source representation would always be the string, but you will be able to know if it was typed as a Number or as a literal String. After that, application’s logic can decide what it should do with it. But yeah, sure, that is a bigger feature А. -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
