NEWS

   1 Bison News
   2 ----------
   3
   4 Changes in version 2.1a:
   5
   6 * %destructor vs. YYABORT, YYACCEPT, and YYERROR.
   7   Destructors are now called when user code invokes YYABORT, YYACCEPT,
   8   and YYERROR, for all objects on the stack, other than objects
   9   corresponding to the right-hand side of the current rule.
  10
  11 * %expect, %expect-rr
  12   Incorrect numbers of expected conflicts are now actual errors,
  13   instead of warnings.
  14
  15 * GLR, YACC parsers.
  16   The %parse-params are available in the %destructor's (and the
  17   experimental %printer's) as per the documentation.
  18
  19 * Bison now warns if it finds a stray `$' or `@' in an action.
  20
  21 * %require "VERSION"
  22   To specify that the grammar file depends on features implemented in
  23   Bison version VERSION or higher.
  24
  25 * lalr1.cc: The token and value types are now class members.
  26   The tokens were defined as free form enums and cpp macros.  YYSTYPE
  27   was defined as a free form union.  They are now class members:
  28   tokens are enumerations of the `yy::parser::token' struct, and the
  29   semantic values have the `yy::parser::semantic_type' type.
  30
  31   If you do not want or can update to this scheme, the directive
  32   `%define "global_tokens_and_yystype" "1"' triggers the global
  33   definition of tokens and YYSTYPE.  This change is suitable both
  34   for previous releases of Bison, and this one.
  35
  36   If you wish to update, then make sure older version of Bison will
  37   fail using `%require "2.1a"'.
  38
  39 * DJGPP support added.
  40
  41 Changes in version 2.1, 2005-09-16:
  42
  43 * The C++ lalr1.cc skeleton supports %lex-param.
  44
  45 * Bison-generated parsers now support the translation of diagnostics like
  46   "syntax error" into languages other than English.  The default
  47   language is still English.  For details, please see the new
  48   Internationalization section of the Bison manual.  Software
  49   distributors should also see the new PACKAGING file.  Thanks to
  50   Bruno Haible for this new feature.
  51
  52 * Wording in the Bison-generated parsers has been changed slightly to
  53   simplify translation.  In particular, the message "memory exhausted"
  54   has replaced "parser stack overflow", as the old message was not
  55   always accurate for modern Bison-generated parsers.
  56
  57 * Destructors are now called when the parser aborts, for all symbols left
  58   behind on the stack.  Also, the start symbol is now destroyed after a
  59   successful parse.  In both cases, the behavior was formerly inconsistent.
  60
  61 * When generating verbose diagnostics, Bison-generated parsers no longer
  62   quote the literal strings associated with tokens.  For example, for
  63   a syntax error associated with '%token NUM "number"' they might
  64   print 'syntax error, unexpected number' instead of 'syntax error,
  65   unexpected "number"'.
  66
  67 Changes in version 2.0, 2004-12-25:
  68
  69 * Possibly-incompatible changes
  70
  71   - Bison-generated parsers no longer default to using the alloca function
  72     (when available) to extend the parser stack, due to widespread
  73     problems in unchecked stack-overflow detection.  You can "#define
  74     YYSTACK_USE_ALLOCA 1" to require the use of alloca, but please read
  75     the manual to determine safe values for YYMAXDEPTH in that case.
  76
  77   - Error token location.
  78     During error recovery, the location of the syntax error is updated
  79     to cover the whole sequence covered by the error token: it includes
  80     the shifted symbols thrown away during the first part of the error
  81     recovery, and the lookahead rejected during the second part.
  82
  83   - Semicolon changes:
  84     . Stray semicolons are no longer allowed at the start of a grammar.
  85     . Semicolons are now required after in-grammar declarations.
  86
  87   - Unescaped newlines are no longer allowed in character constants or
  88     string literals.  They were never portable, and GCC 3.4.0 has
  89     dropped support for them.  Better diagnostics are now generated if
  90     forget a closing quote.
  91
  92   - NUL bytes are no longer allowed in Bison string literals, unfortunately.
  93
  94 * New features
  95
  96   - GLR grammars now support locations.
  97
  98   - New directive: %initial-action.
  99     This directive allows the user to run arbitrary code (including
 100     initializing @$) from yyparse before parsing starts.
 101
 102   - A new directive "%expect-rr N" specifies the expected number of
 103     reduce/reduce conflicts in GLR parsers.
 104
 105   - %token numbers can now be hexadecimal integers, e.g., `%token FOO 0x12d'.
 106     This is a GNU extension.
 107
 108   - The option `--report=lookahead' was changed to `--report=look-ahead'.
 109     The old spelling still works, but is not documented and will be
 110     removed.
 111
 112   - Experimental %destructor support has been added to lalr1.cc.
 113
 114   - New configure option --disable-yacc, to disable installation of the
 115     yacc command and -ly library introduced in 1.875 for POSIX conformance.
 116
 117 * Bug fixes
 118
 119   - For now, %expect-count violations are now just warnings, not errors.
 120     This is for compatibility with Bison 1.75 and earlier (when there are
 121     reduce/reduce conflicts) and with Bison 1.30 and earlier (when there
 122     are too many or too few shift/reduce conflicts).  However, in future
 123     versions of Bison we plan to improve the %expect machinery so that
 124     these violations will become errors again.
 125
 126   - Within Bison itself, numbers (e.g., goto numbers) are no longer
 127     arbitrarily limited to 16-bit counts.
 128
 129   - Semicolons are now allowed before "|" in grammar rules, as POSIX requires.
 130 \f
 131 Changes in version 1.875, 2003-01-01:
 132
 133 * The documentation license has been upgraded to version 1.2
 134   of the GNU Free Documentation License.
 135
 136 * syntax error processing
 137
 138   - In Yacc-style parsers YYLLOC_DEFAULT is now used to compute error
 139     locations too.  This fixes bugs in error-location computation.
 140
 141   - %destructor
 142     It is now possible to reclaim the memory associated to symbols
 143     discarded during error recovery.  This feature is still experimental.
 144
 145   - %error-verbose
 146     This new directive is preferred over YYERROR_VERBOSE.
 147
 148   - #defining yyerror to steal internal variables is discouraged.
 149     It is not guaranteed to work forever.
 150
 151 * POSIX conformance
 152
 153   - Semicolons are once again optional at the end of grammar rules.
 154     This reverts to the behavior of Bison 1.33 and earlier, and improves
 155     compatibility with Yacc.
 156
 157   - `parse error' -> `syntax error'
 158     Bison now uniformly uses the term `syntax error'; formerly, the code
 159     and manual sometimes used the term `parse error' instead.  POSIX
 160     requires `syntax error' in diagnostics, and it was thought better to
 161     be consistent.
 162
 163   - The documentation now emphasizes that yylex and yyerror must be
 164     declared before use.  C99 requires this.
 165
 166   - Bison now parses C99 lexical constructs like UCNs and
 167     backslash-newline within C escape sequences, as POSIX 1003.1-2001 requires.
 168
 169   - File names are properly escaped in C output.  E.g., foo\bar.y is
 170     output as "foo\\bar.y".
 171
 172   - Yacc command and library now available
 173     The Bison distribution now installs a `yacc' command, as POSIX requires.
 174     Also, Bison now installs a small library liby.a containing
 175     implementations of Yacc-compatible yyerror and main functions.
 176     This library is normally not useful, but POSIX requires it.
 177
 178   - Type clashes now generate warnings, not errors.
 179
 180   - If the user does not define YYSTYPE as a macro, Bison now declares it
 181     using typedef instead of defining it as a macro.
 182     For consistency, YYLTYPE is also declared instead of defined.
 183
 184 * Other compatibility issues
 185
 186   - %union directives can now have a tag before the `{', e.g., the
 187     directive `%union foo {...}' now generates the C code
 188     `typedef union foo { ... } YYSTYPE;'; this is for Yacc compatibility.
 189     The default union tag is `YYSTYPE', for compatibility with Solaris 9 Yacc.
 190     For consistency, YYLTYPE's struct tag is now `YYLTYPE' not `yyltype'.
 191     This is for compatibility with both Yacc and Bison 1.35.
 192
 193   - `;' is output before the terminating `}' of an action, for
 194     compatibility with Bison 1.35.
 195
 196   - Bison now uses a Yacc-style format for conflict reports, e.g.,
 197     `conflicts: 2 shift/reduce, 1 reduce/reduce'.
 198
 199   - `yystype' and `yyltype' are now obsolescent macros instead of being
 200     typedefs or tags; they are no longer documented and are planned to be
 201     withdrawn in a future release.
 202
 203 * GLR parser notes
 204
 205   - GLR and inline
 206     Users of Bison have to decide how they handle the portability of the
 207     C keyword `inline'.
 208
 209   - `parsing stack overflow...' -> `parser stack overflow'
 210     GLR parsers now report `parser stack overflow' as per the Bison manual.
 211
 212 * Bison now warns if it detects conflicting outputs to the same file,
 213   e.g., it generates a warning for `bison -d -o foo.h foo.y' since
 214   that command outputs both code and header to foo.h.
 215
 216 * #line in output files
 217   - --no-line works properly.
 218
 219 * Bison can no longer be built by a K&R C compiler; it requires C89 or
 220   later to be built.  This change originally took place a few versions
 221   ago, but nobody noticed until we recently asked someone to try
 222   building Bison with a K&R C compiler.
 223 \f
 224 Changes in version 1.75, 2002-10-14:
 225
 226 * Bison should now work on 64-bit hosts.
 227
 228 * Indonesian translation thanks to Tedi Heriyanto.
 229
 230 * GLR parsers
 231   Fix spurious parse errors.
 232
 233 * Pure parsers
 234   Some people redefine yyerror to steal yyparse' private variables.
 235   Reenable this trick until an official feature replaces it.
 236
 237 * Type Clashes
 238   In agreement with POSIX and with other Yaccs, leaving a default
 239   action is valid when $$ is untyped, and $1 typed:
 240
 241         untyped: ... typed;
 242
 243   but the converse remains an error:
 244
 245         typed: ... untyped;
 246
 247 * Values of mid-rule actions
 248   The following code:
 249
 250         foo: { ... } { $$ = $1; } ...
 251
 252   was incorrectly rejected: $1 is defined in the second mid-rule
 253   action, and is equal to the $$ of the first mid-rule action.
 254 \f
 255 Changes in version 1.50, 2002-10-04:
 256
 257 * GLR parsing
 258   The declaration
 259      %glr-parser
 260   causes Bison to produce a Generalized LR (GLR) parser, capable of handling
 261   almost any context-free grammar, ambiguous or not.  The new declarations
 262   %dprec and %merge on grammar rules allow parse-time resolution of
 263   ambiguities.  Contributed by Paul Hilfinger.
 264
 265   Unfortunately Bison 1.50 does not work properly on 64-bit hosts
 266   like the Alpha, so please stick to 32-bit hosts for now.
 267
 268 * Output Directory
 269   When not in Yacc compatibility mode, when the output file was not
 270   specified, running `bison foo/bar.y' created `foo/bar.c'.  It
 271   now creates `bar.c'.
 272
 273 * Undefined token
 274   The undefined token was systematically mapped to 2 which prevented
 275   the use of 2 by the user.  This is no longer the case.
 276
 277 * Unknown token numbers
 278   If yylex returned an out of range value, yyparse could die.  This is
 279   no longer the case.
 280
 281 * Error token
 282   According to POSIX, the error token must be 256.
 283   Bison extends this requirement by making it a preference: *if* the
 284   user specified that one of her tokens is numbered 256, then error
 285   will be mapped onto another number.
 286
 287 * Verbose error messages
 288   They no longer report `..., expecting error or...' for states where
 289   error recovery is possible.
 290
 291 * End token
 292   Defaults to `$end' instead of `$'.
 293
 294 * Error recovery now conforms to documentation and to POSIX
 295   When a Bison-generated parser encounters a syntax error, it now pops
 296   the stack until it finds a state that allows shifting the error
 297   token.  Formerly, it popped the stack until it found a state that
 298   allowed some non-error action other than a default reduction on the
 299   error token.  The new behavior has long been the documented behavior,
 300   and has long been required by POSIX.  For more details, please see
 301   Paul Eggert, "Reductions during Bison error handling" (2002-05-20)
 302   <http://lists.gnu.org/archive/html/bug-bison/2002-05/msg00038.html>.
 303
 304 * Traces
 305   Popped tokens and nonterminals are now reported.
 306
 307 * Larger grammars
 308   Larger grammars are now supported (larger token numbers, larger grammar
 309   size (= sum of the LHS and RHS lengths), larger LALR tables).
 310   Formerly, many of these numbers ran afoul of 16-bit limits;
 311   now these limits are 32 bits on most hosts.
 312
 313 * Explicit initial rule
 314   Bison used to play hacks with the initial rule, which the user does
 315   not write.  It is now explicit, and visible in the reports and
 316   graphs as rule 0.
 317
 318 * Useless rules
 319   Before, Bison reported the useless rules, but, although not used,
 320   included them in the parsers.  They are now actually removed.
 321
 322 * Useless rules, useless nonterminals
 323   They are now reported, as a warning, with their locations.
 324
 325 * Rules never reduced
 326   Rules that can never be reduced because of conflicts are now
 327   reported.
 328
 329 * Incorrect `Token not used'
 330   On a grammar such as
 331
 332            %token useless useful
 333            %%
 334            exp: '0' %prec useful;
 335
 336   where a token was used to set the precedence of the last rule,
 337   bison reported both `useful' and `useless' as useless tokens.
 338
 339 * Revert the C++ namespace changes introduced in 1.31
 340   as they caused too many portability hassles.
 341
 342 * Default locations
 343   By an accident of design, the default computation of @$ was
 344   performed after another default computation was performed: @$ = @1.
 345   The latter is now removed: YYLLOC_DEFAULT is fully responsible of
 346   the computation of @$.
 347
 348 * Token end-of-file
 349   The token end of file may be specified by the user, in which case,
 350   the user symbol is used in the reports, the graphs, and the verbose
 351   error messages instead of `$end', which remains being the default.
 352   For instance
 353      %token MYEOF 0
 354   or
 355      %token MYEOF 0 "end of file"
 356
 357 * Semantic parser
 358   This old option, which has been broken for ages, is removed.
 359
 360 * New translations
 361   Brazilian Portuguese, thanks to Alexandre Folle de Menezes.
 362   Croatian, thanks to Denis Lackovic.
 363
 364 * Incorrect token definitions
 365   When given `%token 'a' "A"', Bison used to output `#define 'a' 65'.
 366
 367 * Token definitions as enums
 368   Tokens are output both as the traditional #define's, and, provided
 369   the compiler supports ANSI C or is a C++ compiler, as enums.
 370   This lets debuggers display names instead of integers.
 371
 372 * Reports
 373   In addition to --verbose, bison supports --report=THINGS, which
 374   produces additional information:
 375   - itemset
 376     complete the core item sets with their closure
 377   - lookahead [changed to `look-ahead' in 1.875e and later]
 378     explicitly associate look-ahead tokens to items
 379   - solved
 380     describe shift/reduce conflicts solving.
 381     Bison used to systematically output this information on top of
 382     the report.  Solved conflicts are now attached to their states.
 383
 384 * Type clashes
 385   Previous versions don't complain when there is a type clash on
 386   the default action if the rule has a mid-rule action, such as in:
 387
 388       %type <foo> bar
 389       %%
 390       bar: '0' {} '0';
 391
 392   This is fixed.
 393
 394 * GNU M4 is now required when using Bison.
 395 \f
 396 Changes in version 1.35, 2002-03-25:
 397
 398 * C Skeleton
 399   Some projects use Bison's C parser with C++ compilers, and define
 400   YYSTYPE as a class.  The recent adjustment of C parsers for data
 401   alignment and 64 bit architectures made this impossible.
 402
 403   Because for the time being no real solution for C++ parser
 404   generation exists, kludges were implemented in the parser to
 405   maintain this use.  In the future, when Bison has C++ parsers, this
 406   kludge will be disabled.
 407
 408   This kludge also addresses some C++ problems when the stack was
 409   extended.
 410 \f
 411 Changes in version 1.34, 2002-03-12:
 412
 413 * File name clashes are detected
 414   $ bison foo.y -d -o foo.x
 415   fatal error: header and parser would both be named `foo.x'
 416
 417 * A missing `;' at the end of a rule triggers a warning
 418   In accordance with POSIX, and in agreement with other
 419   Yacc implementations, Bison will mandate this semicolon in the near
 420   future.  This eases the implementation of a Bison parser of Bison
 421   grammars by making this grammar LALR(1) instead of LR(2).  To
 422   facilitate the transition, this release introduces a warning.
 423
 424 * Revert the C++ namespace changes introduced in 1.31, as they caused too
 425   many portability hassles.
 426
 427 * DJGPP support added.
 428
 429 * Fix test suite portability problems.
 430 \f
 431 Changes in version 1.33, 2002-02-07:
 432
 433 * Fix C++ issues
 434   Groff could not be compiled for the definition of size_t was lacking
 435   under some conditions.
 436
 437 * Catch invalid @n
 438   As is done with $n.
 439 \f
 440 Changes in version 1.32, 2002-01-23:
 441
 442 * Fix Yacc output file names
 443
 444 * Portability fixes
 445
 446 * Italian, Dutch translations
 447 \f
 448 Changes in version 1.31, 2002-01-14:
 449
 450 * Many Bug Fixes
 451
 452 * GNU Gettext and %expect
 453   GNU Gettext asserts 10 s/r conflicts, but there are 7.  Now that
 454   Bison dies on incorrect %expectations, we fear there will be
 455   too many bug reports for Gettext, so _for the time being_, %expect
 456   does not trigger an error when the input file is named `plural.y'.
 457
 458 * Use of alloca in parsers
 459   If YYSTACK_USE_ALLOCA is defined to 0, then the parsers will use
 460   malloc exclusively.  Since 1.29, but was not NEWS'ed.
 461
 462   alloca is used only when compiled with GCC, to avoid portability
 463   problems as on AIX.
 464
 465 * yyparse now returns 2 if memory is exhausted; formerly it dumped core.
 466
 467 * When the generated parser lacks debugging code, YYDEBUG is now 0
 468   (as POSIX requires) instead of being undefined.
 469
 470 * User Actions
 471   Bison has always permitted actions such as { $$ = $1 }: it adds the
 472   ending semicolon.  Now if in Yacc compatibility mode, the semicolon
 473   is no longer output: one has to write { $$ = $1; }.
 474
 475 * Better C++ compliance
 476   The output parsers try to respect C++ namespaces.
 477   [This turned out to be a failed experiment, and it was reverted later.]
 478
 479 * Reduced Grammars
 480   Fixed bugs when reporting useless nonterminals.
 481
 482 * 64 bit hosts
 483   The parsers work properly on 64 bit hosts.
 484
 485 * Error messages
 486   Some calls to strerror resulted in scrambled or missing error messages.
 487
 488 * %expect
 489   When the number of shift/reduce conflicts is correct, don't issue
 490   any warning.
 491
 492 * The verbose report includes the rule line numbers.
 493
 494 * Rule line numbers are fixed in traces.
 495
 496 * Swedish translation
 497
 498 * Parse errors
 499   Verbose parse error messages from the parsers are better looking.
 500   Before: parse error: unexpected `'/'', expecting `"number"' or `'-'' or `'(''
 501      Now: parse error: unexpected '/', expecting "number" or '-' or '('
 502
 503 * Fixed parser memory leaks.
 504   When the generated parser was using malloc to extend its stacks, the
 505   previous allocations were not freed.
 506
 507 * Fixed verbose output file.
 508   Some newlines were missing.
 509   Some conflicts in state descriptions were missing.
 510
 511 * Fixed conflict report.
 512   Option -v was needed to get the result.
 513
 514 * %expect
 515   Was not used.
 516   Mismatches are errors, not warnings.
 517
 518 * Fixed incorrect processing of some invalid input.
 519
 520 * Fixed CPP guards: 9foo.h uses BISON_9FOO_H instead of 9FOO_H.
 521
 522 * Fixed some typos in the documentation.
 523
 524 * %token MY_EOF 0 is supported.
 525   Before, MY_EOF was silently renumbered as 257.
 526
 527 * doc/refcard.tex is updated.
 528
 529 * %output, %file-prefix, %name-prefix.
 530   New.
 531
 532 * --output
 533   New, aliasing `--output-file'.
 534 \f
 535 Changes in version 1.30, 2001-10-26:
 536
 537 * `--defines' and `--graph' have now an optional argument which is the
 538   output file name. `-d' and `-g' do not change; they do not take any
 539   argument.
 540
 541 * `%source_extension' and `%header_extension' are removed, failed
 542   experiment.
 543
 544 * Portability fixes.
 545 \f
 546 Changes in version 1.29, 2001-09-07:
 547
 548 * The output file does not define const, as this caused problems when used
 549   with common autoconfiguration schemes.  If you still use ancient compilers
 550   that lack const, compile with the equivalent of the C compiler option
 551   `-Dconst='.  autoconf's AC_C_CONST macro provides one way to do this.
 552
 553 * Added `-g' and `--graph'.
 554
 555 * The Bison manual is now distributed under the terms of the GNU FDL.
 556
 557 * The input and the output files has automatically a similar extension.
 558
 559 * Russian translation added.
 560
 561 * NLS support updated; should hopefully be less troublesome.
 562
 563 * Added the old Bison reference card.
 564
 565 * Added `--locations' and `%locations'.
 566
 567 * Added `-S' and `--skeleton'.
 568
 569 * `%raw', `-r', `--raw' is disabled.
 570
 571 * Special characters are escaped when output.  This solves the problems
 572   of the #line lines with path names including backslashes.
 573
 574 * New directives.
 575   `%yacc', `%fixed_output_files', `%defines', `%no_parser', `%verbose',
 576   `%debug', `%source_extension' and `%header_extension'.
 577
 578 * @$
 579   Automatic location tracking.
 580 \f
 581 Changes in version 1.28, 1999-07-06:
 582
 583 * Should compile better now with K&R compilers.
 584
 585 * Added NLS.
 586
 587 * Fixed a problem with escaping the double quote character.
 588
 589 * There is now a FAQ.
 590 \f
 591 Changes in version 1.27:
 592
 593 * The make rule which prevented bison.simple from being created on
 594   some systems has been fixed.
 595 \f
 596 Changes in version 1.26:
 597
 598 * Bison now uses automake.
 599
 600 * New mailing lists: <bug-bison@gnu.org> and <help-bison@gnu.org>.
 601
 602 * Token numbers now start at 257 as previously documented, not 258.
 603
 604 * Bison honors the TMPDIR environment variable.
 605
 606 * A couple of buffer overruns have been fixed.
 607
 608 * Problems when closing files should now be reported.
 609
 610 * Generated parsers should now work even on operating systems which do
 611   not provide alloca().
 612 \f
 613 Changes in version 1.25, 1995-10-16:
 614
 615 * Errors in the input grammar are not fatal; Bison keeps reading
 616 the grammar file, and reports all the errors found in it.
 617
 618 * Tokens can now be specified as multiple-character strings: for
 619 example, you could use "<=" for a token which looks like <=, instead
 620 of chosing a name like LESSEQ.
 621
 622 * The %token_table declaration says to write a table of tokens (names
 623 and numbers) into the parser file.  The yylex function can use this
 624 table to recognize multiple-character string tokens, or for other
 625 purposes.
 626
 627 * The %no_lines declaration says not to generate any #line preprocessor
 628 directives in the parser file.
 629
 630 * The %raw declaration says to use internal Bison token numbers, not
 631 Yacc-compatible token numbers, when token names are defined as macros.
 632
 633 * The --no-parser option produces the parser tables without including
 634 the parser engine; a project can now use its own parser engine.
 635 The actions go into a separate file called NAME.act, in the form of
 636 a switch statement body.
 637 \f
 638 Changes in version 1.23:
 639
 640 The user can define YYPARSE_PARAM as the name of an argument to be
 641 passed into yyparse.  The argument should have type void *.  It should
 642 actually point to an object.  Grammar actions can access the variable
 643 by casting it to the proper pointer type.
 644
 645 Line numbers in output file corrected.
 646 \f
 647 Changes in version 1.22:
 648
 649 --help option added.
 650 \f
 651 Changes in version 1.20:
 652
 653 Output file does not redefine const for C++.
 654
 655 Local Variables:
 656 mode: outline
 657 End:
 658
 659 -----
 660
 661 Copyright (C) 1995, 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005
 662 Free Software Foundation, Inc.
 663
 664 This file is part of Bison, the GNU Compiler Compiler.
 665
 666 Bison is free software; you can redistribute it and/or modify
 667 it under the terms of the GNU General Public License as published by
 668 the Free Software Foundation; either version 2, or (at your option)
 669 any later version.
 670
 671 Bison is distributed in the hope that it will be useful,
 672 but WITHOUT ANY WARRANTY; without even the implied warranty of
 673 MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
 674 GNU General Public License for more details.
 675
 676 You should have received a copy of the GNU General Public License
 677 along with autoconf; see the file COPYING.  If not, write to
 678 the Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor,
 679 Boston, MA 02110-1301, USA.