Floating-point constant tightening.

* parser.l (grammar): Change order of rule which recognizes FLODOT with
a one-character trailing context other than a dot, and the rule which
diagnoses trailing junk. The issue is that this order gives the wrong
interpretation to 123.E, treating it as 123.  followed by E rather than
trailing junk, like in the case of 123.0E or 123.B.

* txr.1: Adding the valid example 1.E5.  Removing references to dot as
consing dot.  Fixed documentation which says that 1.E is 1 followed by
a consing dot and E. The wrong behavior in fact produced 1.0 followed
by E. No consing dot semantics.

1 files changed, 8 insertions, 8 deletions

diff --git a/parser.l b/parser.l
index 2610a921..66a51cfc 100644
--- a/parser.l
+++ b/parser.l
@@ -287,8 +287,12 @@ UONLY   {U2}{U}|{U3}{U}{U}|{U4}{U}{U}{U}
   return NUMBER;
 }
 
-<SPECIAL,QSPECIAL,NESTED,BRACED>{FLODOT}/[^.] {
-  val str = string_own(utf8_dup_from(yytext));
+<SPECIAL>({FLO}|{FLODOT}){TOK} |
+<BRACED>({FLO}|{FLODOT}){BTOK} |
+<NESTED>({FLO}|{FLODOT}){NTOK} {
+  val str = string_utf8(yytext);
+
+  yyerrorf(yyg, lit("trailing junk in floating-point literal: ~a"), str, nao);
 
   if (yy_top_state(yyscanner) == INITIAL
       || yy_top_state(yyscanner) == QSILIT
@@ -299,12 +303,8 @@ UONLY   {U2}{U}|{U3}{U}{U}|{U4}{U}{U}{U}
   return NUMBER;
 }
 
-<SPECIAL>({FLO}|{FLODOT}){TOK} |
-<BRACED>({FLO}|{FLODOT}){BTOK} |
-<NESTED>({FLO}|{FLODOT}){NTOK} {
-  val str = string_utf8(yytext);
-
-  yyerrorf(yyg, lit("trailing junk in floating-point literal: ~a"), str, nao);
+<SPECIAL,QSPECIAL,NESTED,BRACED>{FLODOT}/[^.] {
+  val str = string_own(utf8_dup_from(yytext));
 
   if (yy_top_state(yyscanner) == INITIAL
       || yy_top_state(yyscanner) == QSILIT