GNU bug report logs - #70007
[PATCH] native JSON encoder

Previous Next

Full log

View this message in rfc822 format

From: Eli Zaretskii <eliz <at> gnu.org>
To: Andrea Corallo <acorallo <at> gnu.org>
Cc: mattias.engdegard <at> gmail.com, 70007 <at> debbugs.gnu.org, casouri <at> gmail.com, stefankangas <at> gmail.com, monnier <at> iro.umontreal.ca
Subject: bug#70007: [PATCH] native JSON encoder
Date: Sat, 07 Sep 2024 18:52:49 +0300

> From: Andrea Corallo <acorallo <at> gnu.org>
> Cc: Stefan Kangas <stefankangas <at> gmail.com>,  monnier <at> iro.umontreal.ca,
>   mattias.engdegard <at> gmail.com,  casouri <at> gmail.com,  70007 <at> debbugs.gnu.org
> Date: Sat, 07 Sep 2024 11:48:36 -0400
> 
> Eli Zaretskii <eliz <at> gnu.org> writes:
> 
> >> From: Stefan Kangas <stefankangas <at> gmail.com>
> >> Date: Sat, 31 Aug 2024 15:15:25 -0700
> >> Cc: mattias.engdegard <at> gmail.com, acorallo <at> gnu.org, casouri <at> gmail.com, 
> >> 	70007 <at> debbugs.gnu.org
> >> 
> >> Stefan Monnier <monnier <at> iro.umontreal.ca> writes:
> >> 
> >> >> And against the additional variable to make this more
> >> >> backward-compatible?
> >> >
> >> > Yup.  The var would be my second-best choice (and I assume it's
> >> > immediately declared obsolete).
> >> 
> >> I tend to agree with Stefan M here.
> >
> > Thanks.
> >
> > Andrea, would you please voice your opinion on this?
> 
> I'm for returning unibyte indeed.  And for the variable or the second
> function I'm kind of neutral, I'd do it only if it's not too much effort
> so I'll trust Mattias preference here.

OK, so let's go with unconditionally unibyte, as it seems to be the
consensus here.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.