Fix up invalid_syntax error signalling

* src/lread.c (invalid_syntax_lisp): Instead of putting the
line/column in a string, signal an error containing the numbers as
data.  This allows for easier post-processing and is how other
similar errors (like (forward-sexp 1)) do it.

diff --git a/src/lread.c b/src/lread.c
index 5d1676b0c9c6ad35e8c91ccecf5b45718a8f0fa5..b33a312299f674e5abe80e37afd1d847be9d6e58 100644 (file)
--- a/src/lread.c
+++ b/src/lread.c
@@ -545,14 +545,13 @@ invalid_syntax_lisp (Lisp_Object s, Lisp_Object readcharfun)
 {
   if (BUFFERP (readcharfun))
     {
-      xsignal1 (Qinvalid_read_syntax,
-               CALLN (Fformat, build_string ("%s (line %d, column %d)"),
-                      s,
-                      /* We should already be in the readcharfun
-                         buffer when this error is called, so no need
-                         to switch to it first. */
-                      make_fixnum (count_lines (BEGV_BYTE, PT_BYTE) + 1),
-                      make_fixnum (current_column ())));
+      xsignal (Qinvalid_read_syntax,
+              list3 (s,
+                     /* We should already be in the readcharfun
+                        buffer when this error is called, so no need
+                        to switch to it first. */
+                     make_fixnum (count_lines (BEGV_BYTE, PT_BYTE) + 1),
+                     make_fixnum (current_column ())));
     }
   else
     xsignal1 (Qinvalid_read_syntax, s);