GNU bug report logs - #79192
json parsing error position reform

Previous Next

Full log

Message #50 received at 79192 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Mattias Engdegård <mattias.engdegard <at> gmail.com>
Cc: dmitry <at> gutov.dev, shipmints <at> gmail.com, 79192 <at> debbugs.gnu.org
Subject: Re: bug#79192: json parsing error position reform
Date: Tue, 12 Aug 2025 21:12:54 +0300

> From: Mattias Engdegård <mattias.engdegard <at> gmail.com>
> Date: Tue, 12 Aug 2025 19:53:42 +0200
> Cc: 79192 <at> debbugs.gnu.org,
>  dmitry <at> gutov.dev,
>  shipmints <at> gmail.com
> 
> 11 aug. 2025 kl. 15.40 skrev Eli Zaretskii <eliz <at> gnu.org>:
> 
> > I hear you, but then counting lines in Lisp is simple, and we have
> > functions ready to do that.  So how hard is it to call one of those
> > functions from the parser, when it detects and error and is about to
> > signal?
> 
> The user doesn't care what calculations we make. The values are unused. (And from the user's perspective, undefined.)

If the values are available, whether to use them or not is up to the
callers, I think.  It is none of our business if they don't use them.

Previous Next

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