parser: no string allocation when scanning floats.

Each time the scanner processes a floating-point token,
it allocates a string object, just so it can call flo_str.
The object is then garbage. Let's stop doing that.

* lib.c (flo_str_utf8): New function, closely based on flo_str.
Takes a char * string.

* lib.h (flo_str_utf8): Declared.

* parser.l (out_of_range_float): Take the token as a const
char * string instead of a Lisp string, so we can just pass
yytext to this function.
(grammar): Use flo_str_utf8 instead flo_str, and pass yytext
to out_of_range_float.

* lex.yy.c.shipped: Updated.

1 files changed, 25 insertions, 0 deletions

diff --git a/lib.c b/lib.c
index cf629d6a..987a6b1d 100644
--- a/lib.c
+++ b/lib.c
@@ -5645,6 +5645,31 @@ val int_str(val str, val base)
   return bignum_from_long(value);
 }
 
+val flo_str_utf8(const char *str)
+{
+  char *ptr;
+  double value;
+
+#if CONFIG_LOCALE_TOLERANCE
+  if (dec_point != '.') {
+    size_t size = strlen(str) + 1;
+    char *scopy = alloca(size), *dot = scopy;
+    wmemcpy(scopy, str, size);
+    str = scopy;
+    while ((dot = strchr(dot, '.')) != 0)
+      *dot++ = dec_point;
+  }
+#endif
+
+  value = strtod(str, &ptr);
+
+  if (value == 0 && ptr == str)
+    return nil;
+  if ((value == HUGE_VAL || value == -HUGE_VAL) && errno == ERANGE)
+    return nil;
+  return flo(value);
+}
+
 val flo_str(val str)
 {
   val self = lit("flo-str");