Re: Add a new flag for json_encode
| From: | Andrea Faulds | Date: | Tue, 04 Nov 2014 18:11:18 +0000 |
| Subject: | Re: Add a new flag for json_encode | ||
| References: | 1 2 3 4 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-78657@lists.php.net to get a copy of this message | ||
> On 4 Nov 2014, at 16:41, Ferenc Kovacs <tyra3l@gmail.com> wrote:
>
>
>
> On Tue, Nov 4, 2014 at 5:35 PM, Andrea Faulds <ajf@ajf.me> wrote:
>
> > On 4 Nov 2014, at 14:57, Ferenc Kovacs <tyra3l@gmail.com> wrote:
> >
> > Hi,
> >
> > just a slight correction:
> > as far as I can tell, Jakus was ok with the general idea and even with
> > turning this into the default, but he stated that it should only happen in
> > a major version (as it would cause a slight BC, maybe this could cause
> > problems for some people who are expecting the zeroes to be truncated from
> > integer values) and he also stated that he thinks that there is no reason
> > for a hurry to have this in a micro release, so this could wait until 7.0.
>
> Why would this cause a BC break? If we’re just adding a new, optional, off-by-default option,
> it shouldn’t break anything.
>
> please re-read my previous mail:
> "__turning this into the default__, but he stated that it __should only happen in a major
> version__”
Right, my bad. I read it as “This [including possibly turning this into the default] should only
happen in a major version”, I see what you meant. Sorry for the misunderstanding, in retrospect
the other interpretation would’ve made more sense.
--
Andrea Faulds
http://ajf.me/