GNU bug report logs - #24649
24.5; Why no standard error for "Trailing garbage following expression"?

Previous Next

Full log

View this message in rfc822 format

From: Eli Zaretskii <eliz <at> gnu.org>
To: Lars Ingebrigtsen <larsi <at> gnus.org>
Cc: 24649 <at> debbugs.gnu.org, drew.adams <at> oracle.com
Subject: bug#24649: 24.5; Why no standard error for "Trailing garbage following expression"?
Date: Fri, 23 Aug 2019 12:18:16 +0300

> From: Lars Ingebrigtsen <larsi <at> gnus.org>
> Cc: drew.adams <at> oracle.com,  24649 <at> debbugs.gnu.org
> Date: Fri, 23 Aug 2019 10:16:04 +0200
> 
> >> > +	    xsignal1 (Qinvalid_read_syntax,
> >> > +		      build_string ("Trailing garbage following expression"));
> >> 
> >> There weren't any comments, so I've now applied this.  If somebody has a
> >> better idea for the error signal, please amend.
> >
> > Thanks, but this change needs to be reflected in the ELisp manual,
> > where currently invalid-read-syntax is documented for a different use
> > case.
> 
> Let's see...  Qargs_out_of_range would be inappropriate...  And
> Qwrong_type_argument...  Perhaps the closest one of the predefined
> errors would be Qend_of_file?
> 
> Or we could have a new one.  `garbage-follows-expression'?  That's
> pretty explicit.

We don't have to invent a new symbol, we just need to document in
"Standard errors" that this error is also signaled an the situation
described in this bug report.

Previous Next

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