�ɲɾ�����ӯ�����һ��ˣ��������С���˴��ͣ�������P���ҹ��ñ˽��ά�Բ��������˸߸ԣ�������ơ��ҹ��ñ�����ά�Բ���ˡ���˳^�ӣ������ӡ� ���ͯj�ӣ��ƺ���ӣ� ? PNG ?%k25u25%fgd5n!? PNG ?%k25u25%fgd5n!? PNG ?%k25u25%fgd5n!? PNG ?%k25u25%fgd5n!PKV0]8) AUTHORSnu[Authors of GNU M4. The following contributors have warranted legal paper exchanges with the Free Software Foundation for their contributions to GNU M4. Also see the files ChangeLog and THANKS. This list results from searching for /\bM4\b/ in the file /gd/gnuorg/copyright.list on the fencepost.gnu.org machine. Rene' Seindal seindal@diku.dk 1990-03-28 James L. Avera jima@netcom.com 1993-10-04 Pete Chown pete.chown@dale.dircon.co.uk 1994-06-28 John Gerard Makecki johnm@vlibs.com 1995-04-24 Francois Pinard pinard@iro.umontreal.ca 1996-02-01 Thomas Tanner tanner@ffii.org 1999-06-23 Gary V. Vaughan gary@gnu.org 2000-10-02 Yuji Minejima ? 2001-05-09 Akim Demaille akim@freefriends.org 2001-11-01 Andrew James Bettison andrewb@zip.com.au 2001-11-19 Noah Jeffrey Misch noah@cs.caltech.edu 2004-07-05 Michael Elizabeth Chastain mec@shout.net 2001-12-27 William C. Cox bill@qswtools.com 2004-12-04 Alexandre Duret-Lutz adl@gnu.org 2004-12-04 John Gatewood Ham zappaman@buraphalinux.org 2005-11-01 Eric Benjamin Blake ebb9@byu.net 2006-01-18 John Brzustowski jbrzusto@fastmail.fm 2006-03-06 Ralf Wildenhues Ralf.Wildenhues@gmx.de 2006-03-20 Markus Duft markus.duft@salomon.at 2006-08-03 Joel E. Denny jdenny@clemson.edu 2009-08-18 David Warme David.Warme@Group-W-Inc.com 2010-03-10 Raphael Poss m4-patches@raphael.poss.name 2010-10-04 Tim Rice tim@multitalents.net 2011-01-24 ======================================================================== Copyright (C) 2000, 2006-2007, 2009-2014, 2016 Free Software Foundation, Inc. Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.3 or any later version published by the Free Software Foundation; with no Invariant Sections, with no Front-Cover Texts, and with no Back-Cover Texts. A copy of the license is included in the ``GNU Free Documentation License'' file as part of this distribution. PKV0]ITHANKSnu[GNU M4 THANKS file GNU M4 was originally written by René Seindal. Many people further contributed to GNU M4 by reporting problems, suggesting various improvements or submitting actual code. Here is a list of these people. Help me keep it complete and exempt of errors. Akiko Matsushita matusita@sra.co.jp Akim Demaille demaille@inf.enst.fr Alan Magnuson awm@osc.edu Albert Chin m4-discuss@mlists.thewrittenword.com Alexander Lehmann alex@hal.rhein-main.de Amos Shapira amoss@cs.huji.ac.il Andreas Büning andreas.buening@nexgo.de Andreas Gustafsson gson@niksula.hut.fi Andreas Schultz aschultz@warp10.net Andreas Schwab schwab@ls5.informatik.uni-dortmund.de Assar Westerlund assar@nada.kth.se Ben A. Mesander ben@piglet.cr.usgs.gov Bengt Mertensson bengt@mathematik.uni-bremen.de Bernhard Daeubler daeb@physik.uni-ulm.de Bjorn R. Bjornsson brb@falcon.is Bob Badour bob@badour.net Bob Proulx bob@proulx.com Brendan Kehoe brendan@cygnus.com Bruno Haible bruno@clisp.org Carlo Teubner carlo.teubner@gmail.com Cesar Strauss cestrauss@gmail.com Chris McGuire chris@wso.net Chris Penev xpenev@gmail.com Dagobert Michelsen dagobert@familie-michelsen.de Damian Menscher menscher@uiuc.edu Dan Jacobson jidanni@jidanni.org David J. MacKenzie djm@uunet.uu.net David Perlin davep@nanosoft.com Elbert Pol elbert.pol@gmail.com Elias Benali elptr@users.sourceforge.net Erez Zadok ezk@cs.columbia.edu Eric Allman eric@cs.berkeley.edu Eric Backus ericb@lsid.hp.com Eric Blake ebb9@byu.net Fernando Carrijo fcarrijo1980@gmail.com François Pinard pinard@iro.umontreal.ca Frank Schwidom schwidom@impernet.de Gary V. Vaughan gary@gnu.org Geoff Russell grussell@guest.adelaide.edu.au Giovanni Toffetti toffettg@lu.unisi.ch Giuseppe Scrivano gscrivano@gnu.org Greg A. Woods woods@web.apc.org Hal Peterson hrp@pecan.cray.com Hoang Uong hoang@ornews.intel.com Ian Taylor ian@cygnus.com Ilya N. Golubev gin@mo.msk.ru Jason Merrill jason@jarthur.claremont.edu Jay Krell jay.krell@cornell.edu Jean-Charles Longuet jclonguet@free.fr Jens Rehsack rehsack@googlemail.com Jim Avera jima@netcom.com Jim Kingdom kingdon@cygnus.com Jim Meyering meyering@acm.org Joel E. Denny jdenny@ces.clemson.edu Joel Sherrill jsherril@uahcs2.cs.uah.edu John Brzustowski jbrzusto@fastmail.fm John David Anglin dave@hiauly1.hia.nrc.ca John Gatewood Ham zappaman@buraphalinux.org Josef T. Burger bolo@bolo.com Joseph E. Sacco jsacco@ssl.com Karl Berry karl@freefriends.org Karl Nelson nelson85@llnl.gov Karl Vogel vogelke@c-17igp.wpafb.af.mil Kaveh R. Ghazi ghazi@noc.rutgers.edu KO Myung-Hun komh@chollian.net Konrad Schwarz konrad.schwarz@siemens.com Kristine Lund lund@lpnaxp.in2p3.fr Krste Asanovic krste@icsi.berkeley.edu Lawson Chan Lawson.Chan@tdsecurities.com Marion Hakanson hakanson@cse.ogi.edu Mark Seiden mis@seiden.com Martin Koeppe mkoeppe@gmx.de Matt Kraai kraai@debian.org Matthew Woehlke mw_triad@users.sourceforge.net Matthias Rabe rabe@mathematik.uni-bielefeld.de Michael Fetterman mafetter@ichips.intel.com Michael L. Welcome welcome@bigbird.llnl.gov Mike Dupont jamesmikedupont@googlemail.com Mike Frysinger vapier@gentoo.org Mike Lijewski lijewski@theory.tc.cornell.edu Mike R. mroberge@aol.com Mike Stump mikestump@comcast.net Mikhail Teterin Mikhail.Teterin@murex.com Nelson H. F. Beebe beebe@math.utah.edu Nick S. Kanakakorn skanan@otl.scu.edu Nicolas Lichtmaier nick@technisys.com.ar Nicolas Pioch pioch@inf.enst.fr Noah Friedman friedman@gnu.org Noah Misch noah@cs.caltech.edu Paolo Bonzini bonzini@gnu.org Paul Eggert eggert@cs.ucla.edu Pete Chown pete.chown@dale.dircon.co.uk Pierre Gaumond gaumondp@ere.umontreal.ca Pierre Mathieu mathieu@geod.emr.ca Rainer Tammer tammer@tammer.net Ralf Wildenhues Ralf.Wildenhues@gmx.de René Seindal seindal@diku.dk Richard A Nelson cowboy@vnet.ibm.com Richard Stallman rms@gnu.org Robert Bernstein rocky@panix.com Robert Bihlmeyer robbe@orcus.priv.at Roland H. Pesch roland@wrs.com Roland McGrath roland@gnu.org Ronny Peine RonnyPeine@gmx.de Sami Liedes sliedes@cc.hut.fi Santiago Vila sanvila@debian.org Scott Bartram deneb!scottb Scott McCreary scottmc2@gmail.com Sergey Poznyakoff gray@gnu.org.ua Simon Leinen simon@lia.di.epfl.ch Skip Montanaro skip@automatrix.com Stepan Kasal kasal@ucw.cz Stephen Perkins perkins@cps.msu.edu Steve Williamson willy@uinpla.npl.uiuc.edu Steven Augart saugart@yahoo.com Thomas Klausner tk@giga.or.at Thorsten Ohl ohl@physics.harvard.edu Todd Rinaldo toddr@cpanel.net Tom G. Christensen tgc@jupiterrise.com Tom McConnell tmcconne@sedona.intel.com Tom Quinn trq@dionysos.thphys.ox.ac.uk Tom Tromey tromey@cns.caltech.edu Ulrich Drepper drepper@gnu.org Vern Paxson vern@ee.lbl.gov Vincent Lonngren Vincent.lonngren.759@student.lu.se Vitezslav Crhonek vcrhonek@redhat.com Vivek P. Singhal singhal@cs.utexas.edu Walter Wong wcw+@cmu.edu ======================================================================== Local Variables: coding: utf-8 End: Copyright (C) 2000, 2006-2014, 2016 Free Software Foundation, Inc. Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.3 or any later version published by the Free Software Foundation; with no Invariant Sections, with no Front-Cover Texts, and with no Back-Cover Texts. A copy of the license is included in the ``GNU Free Documentation License'' file as part of this distribution. PKV0]aREADMEnu[GNU `m4' is an implementation of the traditional Unix macro processor. It is mostly SVR4 compatible, although it has some extensions (for example, handling more than 9 positional parameters to macros). `m4' also has built-in functions for including files, running shell commands, doing arithmetic, etc. Autoconf needs GNU `m4' for generating `configure' scripts, but not for running them. GNU `m4' was originally written by Rene' Seindal, from Denmark. This release is considered stable. If GNU `m4' is meant to serve GNU `autoconf', beware that `m4' should be fully installed *prior to* configuring `autoconf' itself. Likewise, if you intend on hacking GNU `m4' from git, the bootstrap process requires that you first install a released copy of GNU `m4'. If you are just trying to build `m4' from a released tarball, you should not normally need to run `./bootstrap' or `autoreconf'; just go ahead and start with `./configure'. If you are trying to build `m4' from git, more information can be found in the version-control-only file HACKING. M4 has an optional dependency on the libsigsegv library: http://www.gnu.org/software/libsigsegv/ If the library has not been installed in the standard location, you can use `./configure --with-libsigsegv-prefix=/path/to/dir', to make the build of `m4' use /path/to/dir/include/sigsegv.h as appropriate. The use of this library is optional; the only difference in having it available is that it increases the number of platforms where `m4' can correctly distinguish stack overflow from an internal bug. It is recommended that you use version 2.9 or newer. In the subdirectory `examples' you will find various m4 files, ranging from trivial test files to rather advanced macros. If you intend to use m4 seriously, you might find useful material down there. See file `BACKLOG' for a summary of pending mail and articles. See file `COPYING' for copying conditions. Note that M4 is distributed under the GNU Public License version 3 or later. Some files in the distribution are copied from the gnulib project, and hence bear the designation version 2 or later because they are unmodified from gnulib; however, if you modify these files using M4 rather than gnulib as the source, you must update the license to be GPLv3 or later. See file `INSTALL' for compilation and installation instructions. See file `NEWS' for a list of major changes in the current release. See file `THANKS' for a list of contributors. By default, the `syscmd' and `esyscmd' macros try to use the first instance of `sh' found by `command -p getconf PATH' at configure time, with a default of `/bin/sh'. If that default is inappropriate, you can use `./configure --with-syscmd-shell=location' to specify the shell to use. By using `./configure --enable-changeword', you get an experimental feature which allows for changing the syntax of what is a "word" in `m4'. This feature will not be present in m4 2.0, but will be replaced by other new features which provide similar capability, so do not count on it. Send bug reports to `bug-m4@gnu.org'. A bug report is an adequate description of the problem: your input, what you expected, what you got, and why this is wrong. Diffs are welcome, but they only describe a solution, from which the problem might be uneasy to infer. For any copyright year range specified as YYYY-ZZZZ in this package note that the range specifies every single year in that closed interval. ======================================================================== Copyright (C) 2000, 2005-2014, 2016 Free Software Foundation, Inc. Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.3 or any later version published by the Free Software Foundation; with no Invariant Sections, with no Front-Cover Texts, and with no Back-Cover Texts. A copy of the license is included in the ``GNU Free Documentation License'' file as part of this distribution. PKV0]~TODOnu[TODO file for GNU m4 Tell if you feel like volunteering for any of these ideas, listed more or less in decreasing order of priority. * Features or problems - Fix format() builtin to handle %c more like printf(1) in the shell http://lists.gnu.org/archive/html/bug-m4/2007-05/msg00047.html Also, gnulib needs help to overcome mingw bugs related to format(). - Update documentation from accumulated mail about it - Study synclines at the very beginning of each diverted sequence - Make eval work on bignums - the 32 bits limit is artificial From Krste Asanovic , 1993-03-20 * Optimization and clean up - Check for memory leaks and uninitialized reads From Vern Paxson on 1993-12-06 - Profile GNU m4 and speed it up From David J. MacKenzie , 1993-01-20 GNU m4 should be sped up by a factor of three for competing with other versions (I think that the lexer is not agressive enough and too often return single characters; obstacks might be a little abused, too). - Have NULs go really undisturbed through GNU m4 See `dumpdef' and debugging section, which abuses %s From Thorsten Ohl , 1992-12-21 path.c (add_include_directory): Why the '\0' terminator? GNU m4 is lousy regarding NULs in streams (this would require maintaining the string lengths, and avoiding strlen, strcpy, etc.). Local Variables: mode: outline outline-regexp: " *[-+*.] \\| " End: Copyright (C) 2000, 2006-2007, 2009-2014, 2016 Free Software Foundation, Inc. Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.3 or any later version published by the Free Software Foundation; with no Invariant Sections, with no Front-Cover Texts, and with no Back-Cover Texts. A copy of the license is included in the ``GNU Free Documentation License'' file as part of this distribution. PKV0]D$~vHH ChangeLognu[2016-12-31 Eric Blake version 1.4.18 * NEWS: Record release date. doc: abbreviate and update release history * doc/m4.texi (History): Shorten, and call out today's release. 2016-12-31 Eric Blake maint: automate creation of release tag The gnulib makefile was already set up to automate things with 'make release ...', but we were still doing things by hand, and thereby risking missing some steps. * m4/gnulib-cache.m4 (gl_MODULES): Import do-release-commit-and-tag. * gnulib: Update, for latest version of the script. * HACKING: Mention its use. 2016-12-31 Eric Blake maint: generate ChangeLog from git commits Follow the practice set in numerous other GNU projects, where the ChangeLog (since 2015) is generated from git commit messages. This avoids duplication or subtle differences between the two, as well as making it easier to merge patches across branches (as good as Bruno Haible's 'git-merge-changelog' helper program is, it still doesn't handle cross-branch cherry-picks very well). * ChangeLog: Move... * ChangeLog-2014: ...to this. * Makefile.am (EXTRA_DIST): Ship renamed file. (gen-ChangeLog): New rule, copied mostly from coreutils. (dist-hook): Generate the ChangeLog. * m4/gnulib-cache.m4 (gl_MODULES): Import gitlog-to-changelog. * .gitignore: Ignore ChangeLog. * .gitattributes: Likewise. * HACKING: Reword to match new procedure, and simplify by referring to an external description of ChangeLog style. 2016-12-31 Eric Blake maint: summarize highlights of pending release * NEWS: Add some blurbs. 2016-12-31 Eric Blake maint: make silent builds the default The user still has full control over verbosity levels, both setting their per-project defaults at configure time (or even in a config.site file), as well as a per-run override. But these days, most projects are defaulting to silent rules without user intervention. * configure.ac (AM_SILENT_RULES): Add, to match what most projects are doing these days. 2016-12-31 Eric Blake maint: release no longer creates a diff file Ever since commit f1cf390 (1.4.14 release), we no longer create diff files as part of the release process. These days, it is assumed that it is easier to download a fresh tarball rather than to try and use a diff file to patch an older tarball. 2016-12-30 Eric Blake doc: drop obsolete @setcontentsaftertitlepage texinfo 6.1 complains (during 'make dvi'): /home/eblake/m4-1.4/doc/./m4.texi:9: @setcontentsaftertitlepage has been remove d as a Texinfo command; move your @contents command if you want the contents af ter the title page.. It turns out that eliminating the command has no effect - modern tools correctly emit the contents in-place, right after the title page, so it was leftover cruft from an older time. * doc/m4.texi: Satisfy newer texinfo. 2016-12-29 Eric Blake build: update to latest gnulib I hit a weird failure during 'make check', and traced it to a recent gnulib regression in parallel test safety. Pick up the gnulib fix. * gnulib: Update to latest, to fix failure in getopt tests. 2016-12-29 Eric Blake maint: regenerate bootstrap Missed during the copyright update. * bootstrap: Regenerate. 2016-12-29 Eric Blake maint: bump copyright year Sadly, there's no commit in 2015, which means we don't get to benefit from using a copyright range. Done with 'make update-copyright'. * all files: Version control now has a commit in 2016. 2016-12-29 Eric Blake gnulib: Update to latest * gnulib: Update to latest. * m4/gnulib-cache.m4: Regenerate. * src/macro.c (expand_macro): Deal with obstack API change. * src/builtin.c (mkstemp_helper): Likewise. PKV0]~MrvrvNEWSnu[GNU M4 NEWS - User visible changes. * Noteworthy changes in release 1.4.18 (2016-12-31) [stable] ** Diagnose --word-regexp as unsupported if it was not configured. ** Preliminary support for OS/2. ** A number of portability improvements inherited from gnulib. * Noteworthy changes in release 1.4.17 (2013-09-22) [stable] ** Fix compilation with newer glibc headers. ** Fix a failure with diverting large amounts of text on mingw (does not affect platforms that can rename an open file). ** A number of portability improvements inherited from gnulib. * Noteworthy changes in release 1.4.16 (2011-03-01) [stable] ** Fix regressions in the `index' builtin. On glibc platforms, this avoids false positives from a strstr bug in glibc 2.9 through 2.12; on many other platforms, it fixes two separate regressions, a false positive introduced in 1.4.11 and a false negative in 1.4.15. ** A number of portability improvements inherited from gnulib. * Noteworthy changes in release 1.4.15 (2010-08-31) [stable] ** Fix regression introduced in 1.4.9b where the `format' builtin could crash on an invalid format string. ** Fix compilation against newer glibc, and on AIX 7.1BETA. ** A number of portability improvements inherited from gnulib. * Noteworthy changes in Version 1.4.14 (2010-02-24) [stable] Released by Eric Blake, based on git version 1.4.13.* ** Fix regression introduced in 1.4.12 where executing with stdout closed could crash m4 on exit on some platforms. ** Fix regressions introduced in 1.4.13 in the `esyscmd' builtin, where closed file descriptors could interfere with child execution, and where a child status of 127 made m4 print a spurious message to stderr. ** Fix a security hole in 'make dist', present since at least M4 1.4, that could affect anybody attempting to redistribute modified sources (see Automake CVE-2009-4029). ** A number of portability improvements inherited from gnulib. * Noteworthy changes in Version 1.4.13 (2009-04-01) [stable] Released by Eric Blake, based on git version 1.4.12.* ** The manual is now distributed under the terms of FDL 1.3. ** The `divert' and `undivert' builtins have been made more efficient when using temporary files for large diversions. ** The `translit' builtin has been made more efficient when the second argument is short. ** The input engine has been optimized for faster processing. ** The command line option `--debugfile', introduced in 1.4.7, now treats its argument as optional, in order to allow setting the debug output back to stderr when used without an argument; and order is now significant with respect to command line files. You must therefore use `m4 --debugfile=trace file', not `m4 file --debugfile trace'. This change does not affect the deprecated `-o'/`--error-output' option. ** The `syscmd' and `esyscmd' builtins can be configured to use an alternate shell, via the new `configure' option `--with-syscmd-shell'. ** A number of portability improvements inherited from gnulib. * Noteworthy changes in Version 1.4.12 (2008-10-10) [stable] Released by Eric Blake, based on git version 1.4.11.* ** Fix regression introduced in 1.4.4b where using `traceon' could delete a macro. This was most noticeable with `traceon(`traceon')', but would also happen in cases such as `foo(traceon(`foo'))'. ** Fix regression introduced in 1.4.7 where `m4 -N9' died with an assertion failure. ** Fix regression introduced in 1.4.11 where `defn' died with an assertion failure on a traced but undefined macro. ** New `-g'/`--gnu' command-line option overrides `-G'/`--traditional'. For now, the environment variable POSIXLY_CORRECT has no effect on M4 behavior; but a future release of M4 will behave as though --traditional is implied if POSIXLY_CORRECT is set (this future change is necessary, because in the current release, there is no way to disable GNU extensions that conflict with POSIX without the use of a non-POSIX command-line argument). Clients of M4 that want to use GNU extensions, even when POSIXLY_CORRECT is set, should start using the -g command-line argument, even though it is currently a no-op if -G did not appear earlier in the command line, so that the client will not break in the face of an upgraded m4 and a POSIXLY_CORRECT execution environment. ** The `-L'/`--nesting-limit' command-line option now defaults to 0 for unlimited on platforms that can detect and deal with stack overflow. On systems that lack alternate stack support, such as Cygwin, and on systems that do not obey the POSIX semantics for distinguishing stack overflow from other exceptions, such as Linux, you can optionally install the libsigsegv library (version 2.6 or newer recommended) to enhance m4's ability to accurately report stack overflow: http://www.gnu.org/software/libsigsegv/ ** A number of portability improvements inherited from gnulib. * Noteworthy changes in Version 1.4.11 (2008-04-02) [stable] Released by Eric Blake, based on git version 1.4.10a ** Security fixes for the -F option, for bugs present since -F was introduced in 1.3: Avoid core dump with 'm4 -F file -t undefined', and avoid arbitrary code execution with certain file names. ** Fix regression introduced in 1.4.9b in the `divert' builtin when more than 512 kibibytes are saved in diversions on platforms like NetBSD or darwin where fopen(name,"a+") seeks to the end of the file. ** The output of the `maketemp' and `mkstemp' builtins is now quoted if a file was created. This is a minor security fix, because it was possible (although rather unlikely) that an unquoted string could match an existing macro name, such that use of the `mkstemp' output would trigger inadvertent macro expansion and operate on the wrong file name. ** Enhance the `defn' builtin to support concatenation of multiple text arguments, as required by POSIX. However, at this time, it is not possible to concatenate a builtin macro with anything else; a warning is now issued if this is attempted, although a future version of M4 may lift this restriction to match other implementations. ** Enhance the `format' builtin to parse all C99 floating point numbers, even on platforms where strtod(3) is buggy, although the replacement function does have the known issue of rounding errors when parsing some decimal floating point values. This fixes testsuite failures introduced in 1.4.9b. ** Enhance the `index' builtin to guarantee linear behavior, in spite of the surprisingly large number of systems with a brain-dead quadratic strstr(3). ** A number of portability improvements inherited from gnulib. * Noteworthy changes in Version 1.4.10 (2007-07-09) [stable] Released by Eric Blake, based on CVS version 1.4.9c ** Upgrade from GPL version 2 to GPL version 3 or later. ** A number of portability improvements inherited from gnulib. ** Avoid undefined behavior introduced in 1.4.9b in the `format' builtin when handling %c. However, this area of code has never been documented, and currently does not match the POSIX behavior of printf(1), so it may have further changes in the next version. * Noteworthy changes in Version 1.4.9b (2007-05-29) [beta] Released by Eric Blake, based on CVS version 1.4.9a ** Fix regression introduced in 1.4.9 in the `eval' builtin when performing division. ** Fix regression introduced in 1.4.8 in the `-F' option that made it impossible to freeze more than 512 kibibytes of diverted text. ** The synclines option `-s' no longer generates sync lines in the middle of multiline comments or quoted strings. ** Work around a number of corner-case POSIX compliance bugs in various broken stdio libraries. In particular, the `syscmd' builtin behaves more predictably when stdin is seekable. ** The `format' builtin now understands formats such as %a, %A, and %'hhd, and works around a number of platform printf bugs. Furthermore, the sequence format(%*.*d,-1,-1,1) no longer outputs random data. However, some non-compliant platforms such as mingw still have known bugs in strtod that may cause testsuite failures. ** The testsuite is improved to also run gnulib portability tests for the features that M4 imports from gnulib. * Noteworthy changes in Version 1.4.9 (2007-03-23) [stable] Released by Eric Blake, based on CVS version 1.4.8c ** Minor documentation and portability cleanups. * Noteworthy changes in Version 1.4.8b (2007-02-24) [beta] Released by Eric Blake, based on CVS version 1.4.8a ** Fix a regression introduced in 1.4.8 that made m4 unable to process files larger than 2GiB on some platforms. ** Fix a regression introduced in 1.4.8 that made m4 dump core when invoked as 'm4 -- file'. ** The `eval' builtin now follows C precedence rules. Additionally, the short-circuit operators correctly short-circuit division by zero. The previously undocumented alias of '=' meaning '==' in eval now triggers a deprecation warning, so that a future version of M4 can implement a form of variable assignment as an extension. ** The `include' builtin now affects exit status on failure, as required by POSIX. Use `sinclude' if you need a successful exit status. ** The `-E'/`--fatal-warnings' command-line option now has two levels. When specified only once, warnings affect exit status, but execution continues, so that you can see all warnings instead of fixing them one at a time. To achieve 1.4.8 behavior, where the first warning immediately exits, specify -E twice on the command line. ** A new `--warn-macro-sequence' command-line option allows detection of sequences in `define' and `pushdef' definitions that match an optional regular expression. The default regular expression is `\$\({[^}]*}\|[0-9][0-9]+\)', corresponding to the sequences that might not behave correctly when upgrading to the eventual M4 2.0. By default, M4 2.0 will follow the POSIX requirement that a macro definition containing `$11' must expand to the first argument concatenated with 1, rather than the eleventh argument; and will take advantage of the POSIX wording that allows implementations to treat `${11}' as the eleventh argument instead of literal text. Be aware that Autoconf 2.61 will not work with this option enabled with the default regular expression; but Autoconf 2.62 will be compatible with this option. ** Improved portability to platforms such as BSD/OS and AIX. * Noteworthy changes in Version 1.4.8 (2006-11-20) [stable] Released by Eric Blake, based on CVS version 1.4.7a ** The `divert' macro and `-H'/`--hashsize' command line option no longer cause a core dump when handed extra large values. Also, `divert' now uses memory proportional to the number of diversions in use, rather than to the maximum diversion number encountered, so that large diversion numbers are less likely to exhaust system memory; and is no longer limited by the maximum number of file descriptors. ** The `--help' and `--version' command line options now consistently override all earlier options. For example, `m4 --debugfile=trace --help' now no longer accidentally creates an empty file `trace'. ** The `-L'/`--nesting-limit' command line option can now be set to 0 to remove the default limit of 1024. However, it is still possible that heavily nested input can cause abrupt program termination due to stack overflow. ** Problems encountered when writing to standard error, such as with the `errprint' macro, now always cause a non-zero exit status. ** Warnings and errors issued during macro expansion are now consistently reported at the line where the macro name was detected, rather than where the close parenthesis resides. Text wrapped by `m4wrap' now remembers the location that was in effect when m4wrap was invoked, rather than changing to line 0 and the empty string for a file. The macros `__line__' and `__file__' now work correctly even as the last token in an included file. ** The `builtin' and `indir' macros now transparently handle builtin tokens generated by `defn'. ** When diversions created by the `divert' macro collect enough text that M4 must use temporary files, the environment variable $TMPDIR is now consulted, and a better effort is made to clean up those files in the event of a fatal signal. ** The `mkstemp' builtin is added with the same GNU semantics as `maketemp', based on the recommendation of POSIX to deprecate the POSIX semantics of `maketemp' as inherently insecure. In GNU mode (no -G supplied on the command line), `maketemp' silently retains the secure GNU semantics, but a future release of M4 will change this to emit a warning. In traditional mode (m4 -G), `maketemp' now uses the POSIX-mandated insecure semantics, and issues a warning that you should convert your script to use `mkstemp' instead. Additionally, `mkstemp' and `maketemp' are now well-defined even if the template argument does not end in six `X' characters. ** The manual has been improved, including a new section on a composite macro `foreach'. ** The `changecom' and `changequote' macros now treat an empty second argument the same as if it were missing, rather than using the empty string and making it impossible to end a comment or quote. ** The `translit' macro now operates in linear instead of quadratic time, and is now eight-bit clean. ** The `-D', `-U', `-s', and `-t' command line options now take effect after any files encountered earlier on the command line, rather than up front, as is done in traditional implementations and required by POSIX. * Noteworthy changes in Version 1.4.7 (2006-09-25) [stable] Released by Eric Blake, based on CVS version 1.4.6a ** Fix regression from 1.4.5 in handling a file that ends in a macro expansion without arguments instead of a newline. ** The define and pushdef macros now warn when the first argument is not a string, rather than silently doing nothing. ** Standard input can now be read more than once, as in 'm4 - file -', and is not closed until all wrapped text is handled. This makes a difference when stdin is not a regular file, and also fixes bugs when using the syscmd or esyscmd macros from wrapped text. ** When standard input is a seekable file, the m4exit, syscmd, and esyscmd macros now restore the current position to the next unread byte rather than discarding an arbitrary amount of buffered data. ** SysV command-line compatibility is no longer a goal of GNU M4; the focus will be instead on POSIX compatibility. This release continues to support previous usage, but adds warnings in areas which will allow a future version of GNU M4 to use its own extensions without being tied to the SysV command line interface. ** The no-op compatibility command line options -B, -N, -S, -T, and --diversions may be withdrawn or assigned new meanings in future releases, so they now issue a warning if used. ** A new command line option -i replaces the compatibility -e as the short spelling of --interactive, for consistency with other GNU tools; a warning is issued if the old spelling is used, and it may be assigned new meaning in future releases. ** A new command line option --debugfile replaces the options -o and --error-output as the preferred spelling. The old options were misleading in their names and inconsistent with other GNU tools; they are still silently accepted, but no longer documented in --help, and may be assigned new meanings in future releases. * Noteworthy changes in Version 1.4.6 (2006-08-25) [stable] Released by Eric Blake, based on CVS version 1.4.5a ** Fix buffer overruns in regexp and patsubst macros when handed a trailing backslash in the replacement text, or when handling \n substitutions beyond the number of \(\) groups. ** Fix memory leak in regexp, patsubst, and changeword macros. ** The format macro now understands %F, %g, and %G. ** When loading frozen files, m4 now exits with status 63 if version mismatch is detected. ** Fix bugs that occurred when invoked with stdout or stderr closed, and detect write failures to stdout or to the target of the debugfile macro. In particular, the syscmd and esyscmd macros can no longer interfere with the debug stream or diversions. ** The m4exit macro now converts values outside the range 0-255 to 1. ** It is now an error if a command-line input file ends in the middle of a comment, matching the behavior of mid-string and mid-argument collection. ** The dnl macro now warns if end of file is encountered instead of a newline. ** The error message when end of file is encountered now uses the file and line where the dangling construct started, rather than `NONE:0:'. ** The debugmode and __file__ macros, and the -s/--synclines option, now show what directory a file was found in when the -I/--include option or M4PATH variable had an effect. ** The changequote and changecom macros now work with 8-bit characters, and quotes and comments that begin with `(' are properly recognized following a word. ** The new macro __program__ is added, which allows the input file to issue an error message that resembles messages from m4. Warning and error messages have been reformatted to comply with GNU Coding Standards. ** The errprint, m4wrap, and shift macros are now recognized only with arguments. ** The index, substr, translit, regexp, and patsubst macros now produce output when given only one argument, but still warn about a missing second argument. ** The patsubst macro now reliably finds zero-length matches at the end of a string. * Noteworthy changes in Version 1.4.5 (2006-07-15) [stable] Released by Eric Blake, based on CVS version 1.4.4c ** Fix sysval on BeOS, OS/2, and other systems that store exit status in the low-order byte. Additionally, on Unix platforms, if syscmd was terminated by a signal, sysval now displays the signal number shifted left by eight bits, to match traditional m4 implementations. ** The maketemp macro is no longer subject to platform limitations (such as 26 or 32 max files from a given template). ** Frozen files now require that the first directive be V (version), to better diagnose version mismatch. Additionally, if the F directive (builtin function) names an unknown builtin that existed in the m4 that froze the file but not in the current m4 (for example, changeword), the warning is deferred until an attempt is made to actually use the builtin. This allows downgrading from beta m4-1.4o to stable m4-1.4.5 without breaking autoconf. ** The format and indir macros are now recognized only with arguments. ** The eval macro no longer crashes on x86 architectures when dividing the minimum integer by -1. ** On systems with ecvt and fcvt, format no longer truncates trailing zeroes on integers printed with %.0f. On systems without these functions, format is no longer subject to a buffer overflow that permitted arbitrary code execution. ** On native Windows builds, the macro __windows__ is provided instead of __unix__. Likewise, on OS/2 builds, the macro __os2__ is provided. This allows input files to determine when syscmd might behave differently. ** Fix bug in 1.4.3 patch to use \n line-endings that did not work for cygwin. ** When given the empty string or 0, undivert is now documented as a no-op rather than closing stdout, warning about a non-existent file, or trying to read a directory as a file. ** Many documentation improvements. Also, the manual is now distributed under FDL 1.2, rather than a stricter verbatim-only license. ** Raise the -L (--nesting-limit) command line option limit from 250 to 1024. ** The decr, incr, divert, m4exit, and substr macros treat an empty number as 0, issue a warning, and expand as normal; rather than issuing an error and expanding to the empty string. ** The eval macro now treats an empty radix argument as 10, handles radix 1, and treats the width argument as number of digits excluding the sign, for compatibility with other m4 implementations. ** The ifdef, divert, m4exit, substr, and translit macros now correctly ignore extra arguments. ** The popdef and undefine macros now correctly accept multiple arguments. ** Although changeword is on its last leg, if enabled, it now reverts to the default (faster) regexp when passed the empty string. ** The regexp and substr macros now warn and ignore a trailing backslash in the replacement, and warn on \n for n larger than the number of sub-expressions in the regexp. * Noteworthy changes in Version 1.4.4b (2006-06-17) [beta] Released by Eric Blake, based on CVS version 1.4.4a ** Fix a recursive push_string crashing bug, which affected changequote of three or more characters on some compilers. ** Use automake to fix build portability issues. ** Fix a recursive m4wrap crashing bug. ** Fix a 1 in 2**32 hash crashing bug. ** Tracing a macro by name is now persistent, even if the macro is subsequently undefined or redefined. The traceon and traceoff macros no longer warn about undefined symbols. This solves a crash when using indir on an undefined macro traced with the -t option, as well as an incorrect result of ifdef. Furthermore, tracing is no longer transferred with builtins, solving the bug of "m4 -tm4_eval" failing to give trace output on the input "define(`m4_eval',defn(`eval'))m4_eval(1)". ** Fix a crash when a macro is undefined while collecting its arguments, by always using the definition that was in effect before argument collection. This behavior matches the C pre-processor, and means that the sequence "define(`f',`1')f(define(`f',`2'))f" is now documented to result in "12", rather than the previously undocumented "22". ** Update the regex engine to fix several bugs. ** Fix a potential crash on machines where char is signed. * Noteworthy changes in Version 1.4.4 (Oct 2005) [stable] Released by Gary V. Vaughan ** ./configure --infodir=/usr/share/info now works correctly. ** When any file named on the command line is missing exit with status 1. * Noteworthy changes in Version 1.4.3 (Mar 2005) [stable] Released by Gary V. Vaughan ** DESTDIR installs now work correctly. ** Don't segfault with uncompilable regexps to changeword(). ** Always use \n line-endings for frozen files (fixes a Windows bug). ** Portability fix for systems lacking mkstemp(3). ** Approximately 20% speed up in the common case of usage with autoconf. ** Supported on QNX 6.3. * Noteworthy changes in Version 1.4.2 (Aug 2004) [stable] Released by Paul Eggert ** No user visible changes; portability bug fixes only. * Noteworthy changes in Version 1.4.1 (Jun 2004) [stable] Released by Paul Eggert ** maketemp now creates an empty file with the given name, instead of merely returning the name of a nonexistent file. This closes a security hole. * Noteworthy changes in Version 1.4 (Oct 1994) [stable] Released by Franc,ois Pinard ** (No user visible changes) Version 1.3 - September 1994, by Franc,ois Pinard * Diversions are created as needed. Option `-N' is still accepted, but otherwise ignored. Users should use only negative diversion numbers, instead of high positive numbers, for diverting to nowhere. * Diversions should also work faster. No temporary files will be needed at all if all diversions taken altogether do not use more than 512K. * Frozen state files may be produced with the `--freeze-state' (-F) option and later brought back through the `--reload-state' (-R) option. Version 1.2 - July 1994, by Franc,ois Pinard * In patsubst(STRING, REGEXP, REPLACEMENT), \& in REPLACEMENT has been changed to represent this part of STRING matched by the whole REGEXP, instead of the whole STRING as before. \0 does the same, but emits a diagnostic saying it will disappear in some subsequent release. * eval(EXPR) emits a diagnostic if EXPR has suffixed crumb. The same for other numeric conversions in incr(), decr(), divert(), etc. * `--fatal-warnings' (-E) stops execution at first warning. * `--nesting-limit=LEVEL' (-L LEVEL) sets a limit to macro nesting. It is initially fixed at 250. * `--word-regexp=REGEXP' (-W REGEXP) modifies macro name syntax, like does the new `changeword(REGEXP)' macro. This feature is experimental, tell me your opinions about it. You do need --enable-changeword at configure time to get these things. Do *not* depend on them yet. * Trace output format is scannable by GNU Emacs' next-error function. * Stack overflow is detected and diagnosed on some capable systems. * Various bugs have been corrected, m4 should be more portable. See the ChangeLog for details. Version 1.1 - November 1993, by Franc,ois Pinard Changes which might affect existing GNU m4 scripts: * Option `-V' has been removed, use `--version' instead. `--version' writes on standard output instead of standard error, and inhibits any script execution. * `--no-gnu-extensions' has been renamed `--traditional'. * In `eval', `^' used to indicate exponentiation, use `**' instead. * The automatic undiversion which takes place at end of all input is forced into the main output stream. Changes which are unlikely to affect existing scripts: * `--help' prints an usage summary on standard output. Script execution is then inhibited. * `--prefix-builtins' (-P) prefixes all builtin macros by `m4_'. * Most builtin macros for which arguments are mandatory, called without any arguments, are no more recognized as builtin macros: they are consequently copied verbatim to the output stream. * `define' and `pushdef' are usable with only one argument, they give this argument an empty definition. * `eval' new operators for binary representation handling: `^' for exclusive-or, `~' for the bitwise negation, `<<' and `>>' for shifts. * `eval' recognizes the notation 0bDIGITS for binary numbers and the notation 0rRADIX:DIGITS for numbers in any radix from 1 to 36. Version 1.0.3 - December 1992, by Franc,ois Pinard Changes for the user: * `dnl' outputs a diagnostic if immediately followed by `('. Usually, `dnl' is followed by newline or whitespace. * `ifelse' accepts without complaining the common idiom of having only one argument. This is useful for introducing long comments. * `eval' always expresses values as signed, whatever the radix. * M4OPTS environment variable is no longer obeyed. * `--no-warnings' option is renamed `--silent'. * Debug lines use a new format more compatible with GNU standards. * Various bugs have been corrected. See the ChangeLog for details. Changes for the installer: * GNU m4 now uses an Autoconf-generated configure script, and should be more easily portable in many ways. (Cray is not supported yet). * `make check' has been made more portable, expect no errors. Changes for the programmer: * Sources have been fully reindented to comply with GNU standards, and cleaned up in many ways. * Sources have been protoized. Non-ANSI compilers are automatically detected, then sources are unprotoized on the fly before compilation. * GNU m4 uses newer versions of obstack, regex, getopt, etc. Version 1.0 - October 1991, by Rene' Seindal * Uses GNU configure, taken from the gdb distribution. * Uses GNU getopt(), with long option names. * The -Q/+quiet option is added, which suppresses warnings about missing or superflous arguments to built-in macros. * Added default options via the M4OPTS environment variable. * Several minor bugs have been fixed. Version 0.99 - July 1991, by Rene' Seindal * The builtins `incr' and `decr' are now implemented without use of `eval'. * The builtin `indir' is added, to allow for indirect macro calls (allows use of "illegal" macro names). * The debugging and tracing facilities has been enhanced considerably. See the manual for details. * The -tMACRO option is added, marks MACRO for tracing as soon as it is defined. * Builtins are traced after renaming iff they were before. * Named files can now be undiverted. * The -Nnum option can be used to increase the number of divertions available. * Calling changecom without arguments now disables all comment handling. * A bug in `dnl' is fixed. * A bug in the multi-character quoting code is fixed. * Several typos in the manual has been corrected. More probably persist. Version 0.75 - November 1990, by Rene' Seindal * Implemented search path for include files (-I option and M4PATH environment variable). * Implemented builtin `format' for printf-like formatting. * Implemented builtin `regexp' for searching for regular expressions. * Implemented builtin `patsubst' for substitution with regular expressions. * Implemented builtin `esyscmd', which expands to a shell commands output. * Implemented `__file__' and `__line__' for use in error messages. * Implemented character ranges in `translit'. * Implemented control over debugging output. * Implemented multi-character quotes. * Implemented multi-character comment delimiters. * Changed predefined macro `gnu' to `__gnu__'. * Changed predefined macro `unix' to `__unix__', when the -G option is not used. With -G, `unix' is still defined. * Added program name to error messages. * Fixed two missing null bytes bugs. Version 0.50 - January 1990, by Rene' Seindal * Initial beta release. ======================================================================== Local Variables: mode: outline fill-column: 75 End: Copyright (C) 1992-1994, 2004-2014, 2016 Free Software Foundation, Inc. Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.3 or any later version published by the Free Software Foundation; with no Invariant Sections, with no Front-Cover Texts, and with no Back-Cover Texts. A copy of the license is included in the ``GNU Free Documentation License'' file as part of this distribution. PKn1]|wfKKCOPYINGnu[ GNU GENERAL PUBLIC LICENSE Version 3, 29 June 2007 Copyright (C) 2007 Free Software Foundation, Inc. Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed. Preamble The GNU General Public License is a free, copyleft license for software and other kinds of works. The licenses for most software and other practical works are designed to take away your freedom to share and change the works. By contrast, the GNU General Public License is intended to guarantee your freedom to share and change all versions of a program--to make sure it remains free software for all its users. We, the Free Software Foundation, use the GNU General Public License for most of our software; it applies also to any other work released this way by its authors. You can apply it to your programs, too. When we speak of free software, we are referring to freedom, not price. Our General Public Licenses are designed to make sure that you have the freedom to distribute copies of free software (and charge for them if you wish), that you receive source code or can get it if you want it, that you can change the software or use pieces of it in new free programs, and that you know you can do these things. To protect your rights, we need to prevent others from denying you these rights or asking you to surrender the rights. Therefore, you have certain responsibilities if you distribute copies of the software, or if you modify it: responsibilities to respect the freedom of others. For example, if you distribute copies of such a program, whether gratis or for a fee, you must pass on to the recipients the same freedoms that you received. You must make sure that they, too, receive or can get the source code. And you must show them these terms so they know their rights. Developers that use the GNU GPL protect your rights with two steps: (1) assert copyright on the software, and (2) offer you this License giving you legal permission to copy, distribute and/or modify it. For the developers' and authors' protection, the GPL clearly explains that there is no warranty for this free software. For both users' and authors' sake, the GPL requires that modified versions be marked as changed, so that their problems will not be attributed erroneously to authors of previous versions. Some devices are designed to deny users access to install or run modified versions of the software inside them, although the manufacturer can do so. This is fundamentally incompatible with the aim of protecting users' freedom to change the software. The systematic pattern of such abuse occurs in the area of products for individuals to use, which is precisely where it is most unacceptable. Therefore, we have designed this version of the GPL to prohibit the practice for those products. If such problems arise substantially in other domains, we stand ready to extend this provision to those domains in future versions of the GPL, as needed to protect the freedom of users. Finally, every program is threatened constantly by software patents. States should not allow patents to restrict development and use of software on general-purpose computers, but in those that do, we wish to avoid the special danger that patents applied to a free program could make it effectively proprietary. To prevent this, the GPL assures that patents cannot be used to render the program non-free. The precise terms and conditions for copying, distribution and modification follow. TERMS AND CONDITIONS 0. Definitions. "This License" refers to version 3 of the GNU General Public License. "Copyright" also means copyright-like laws that apply to other kinds of works, such as semiconductor masks. "The Program" refers to any copyrightable work licensed under this License. Each licensee is addressed as "you". "Licensees" and "recipients" may be individuals or organizations. To "modify" a work means to copy from or adapt all or part of the work in a fashion requiring copyright permission, other than the making of an exact copy. The resulting work is called a "modified version" of the earlier work or a work "based on" the earlier work. A "covered work" means either the unmodified Program or a work based on the Program. To "propagate" a work means to do anything with it that, without permission, would make you directly or secondarily liable for infringement under applicable copyright law, except executing it on a computer or modifying a private copy. Propagation includes copying, distribution (with or without modification), making available to the public, and in some countries other activities as well. To "convey" a work means any kind of propagation that enables other parties to make or receive copies. Mere interaction with a user through a computer network, with no transfer of a copy, is not conveying. An interactive user interface displays "Appropriate Legal Notices" to the extent that it includes a convenient and prominently visible feature that (1) displays an appropriate copyright notice, and (2) tells the user that there is no warranty for the work (except to the extent that warranties are provided), that licensees may convey the work under this License, and how to view a copy of this License. If the interface presents a list of user commands or options, such as a menu, a prominent item in the list meets this criterion. 1. Source Code. The "source code" for a work means the preferred form of the work for making modifications to it. "Object code" means any non-source form of a work. A "Standard Interface" means an interface that either is an official standard defined by a recognized standards body, or, in the case of interfaces specified for a particular programming language, one that is widely used among developers working in that language. The "System Libraries" of an executable work include anything, other than the work as a whole, that (a) is included in the normal form of packaging a Major Component, but which is not part of that Major Component, and (b) serves only to enable use of the work with that Major Component, or to implement a Standard Interface for which an implementation is available to the public in source code form. A "Major Component", in this context, means a major essential component (kernel, window system, and so on) of the specific operating system (if any) on which the executable work runs, or a compiler used to produce the work, or an object code interpreter used to run it. The "Corresponding Source" for a work in object code form means all the source code needed to generate, install, and (for an executable work) run the object code and to modify the work, including scripts to control those activities. However, it does not include the work's System Libraries, or general-purpose tools or generally available free programs which are used unmodified in performing those activities but which are not part of the work. For example, Corresponding Source includes interface definition files associated with source files for the work, and the source code for shared libraries and dynamically linked subprograms that the work is specifically designed to require, such as by intimate data communication or control flow between those subprograms and other parts of the work. The Corresponding Source need not include anything that users can regenerate automatically from other parts of the Corresponding Source. The Corresponding Source for a work in source code form is that same work. 2. Basic Permissions. All rights granted under this License are granted for the term of copyright on the Program, and are irrevocable provided the stated conditions are met. This License explicitly affirms your unlimited permission to run the unmodified Program. The output from running a covered work is covered by this License only if the output, given its content, constitutes a covered work. This License acknowledges your rights of fair use or other equivalent, as provided by copyright law. You may make, run and propagate covered works that you do not convey, without conditions so long as your license otherwise remains in force. You may convey covered works to others for the sole purpose of having them make modifications exclusively for you, or provide you with facilities for running those works, provided that you comply with the terms of this License in conveying all material for which you do not control copyright. Those thus making or running the covered works for you must do so exclusively on your behalf, under your direction and control, on terms that prohibit them from making any copies of your copyrighted material outside their relationship with you. Conveying under any other circumstances is permitted solely under the conditions stated below. Sublicensing is not allowed; section 10 makes it unnecessary. 3. Protecting Users' Legal Rights From Anti-Circumvention Law. No covered work shall be deemed part of an effective technological measure under any applicable law fulfilling obligations under article 11 of the WIPO copyright treaty adopted on 20 December 1996, or similar laws prohibiting or restricting circumvention of such measures. When you convey a covered work, you waive any legal power to forbid circumvention of technological measures to the extent such circumvention is effected by exercising rights under this License with respect to the covered work, and you disclaim any intention to limit operation or modification of the work as a means of enforcing, against the work's users, your or third parties' legal rights to forbid circumvention of technological measures. 4. Conveying Verbatim Copies. You may convey verbatim copies of the Program's source code as you receive it, in any medium, provided that you conspicuously and appropriately publish on each copy an appropriate copyright notice; keep intact all notices stating that this License and any non-permissive terms added in accord with section 7 apply to the code; keep intact all notices of the absence of any warranty; and give all recipients a copy of this License along with the Program. You may charge any price or no price for each copy that you convey, and you may offer support or warranty protection for a fee. 5. Conveying Modified Source Versions. You may convey a work based on the Program, or the modifications to produce it from the Program, in the form of source code under the terms of section 4, provided that you also meet all of these conditions: a) The work must carry prominent notices stating that you modified it, and giving a relevant date. b) The work must carry prominent notices stating that it is released under this License and any conditions added under section 7. This requirement modifies the requirement in section 4 to "keep intact all notices". c) You must license the entire work, as a whole, under this License to anyone who comes into possession of a copy. This License will therefore apply, along with any applicable section 7 additional terms, to the whole of the work, and all its parts, regardless of how they are packaged. This License gives no permission to license the work in any other way, but it does not invalidate such permission if you have separately received it. d) If the work has interactive user interfaces, each must display Appropriate Legal Notices; however, if the Program has interactive interfaces that do not display Appropriate Legal Notices, your work need not make them do so. A compilation of a covered work with other separate and independent works, which are not by their nature extensions of the covered work, and which are not combined with it such as to form a larger program, in or on a volume of a storage or distribution medium, is called an "aggregate" if the compilation and its resulting copyright are not used to limit the access or legal rights of the compilation's users beyond what the individual works permit. Inclusion of a covered work in an aggregate does not cause this License to apply to the other parts of the aggregate. 6. Conveying Non-Source Forms. You may convey a covered work in object code form under the terms of sections 4 and 5, provided that you also convey the machine-readable Corresponding Source under the terms of this License, in one of these ways: a) Convey the object code in, or embodied in, a physical product (including a physical distribution medium), accompanied by the Corresponding Source fixed on a durable physical medium customarily used for software interchange. b) Convey the object code in, or embodied in, a physical product (including a physical distribution medium), accompanied by a written offer, valid for at least three years and valid for as long as you offer spare parts or customer support for that product model, to give anyone who possesses the object code either (1) a copy of the Corresponding Source for all the software in the product that is covered by this License, on a durable physical medium customarily used for software interchange, for a price no more than your reasonable cost of physically performing this conveying of source, or (2) access to copy the Corresponding Source from a network server at no charge. c) Convey individual copies of the object code with a copy of the written offer to provide the Corresponding Source. This alternative is allowed only occasionally and noncommercially, and only if you received the object code with such an offer, in accord with subsection 6b. d) Convey the object code by offering access from a designated place (gratis or for a charge), and offer equivalent access to the Corresponding Source in the same way through the same place at no further charge. You need not require recipients to copy the Corresponding Source along with the object code. If the place to copy the object code is a network server, the Corresponding Source may be on a different server (operated by you or a third party) that supports equivalent copying facilities, provided you maintain clear directions next to the object code saying where to find the Corresponding Source. Regardless of what server hosts the Corresponding Source, you remain obligated to ensure that it is available for as long as needed to satisfy these requirements. e) Convey the object code using peer-to-peer transmission, provided you inform other peers where the object code and Corresponding Source of the work are being offered to the general public at no charge under subsection 6d. A separable portion of the object code, whose source code is excluded from the Corresponding Source as a System Library, need not be included in conveying the object code work. A "User Product" is either (1) a "consumer product", which means any tangible personal property which is normally used for personal, family, or household purposes, or (2) anything designed or sold for incorporation into a dwelling. In determining whether a product is a consumer product, doubtful cases shall be resolved in favor of coverage. For a particular product received by a particular user, "normally used" refers to a typical or common use of that class of product, regardless of the status of the particular user or of the way in which the particular user actually uses, or expects or is expected to use, the product. A product is a consumer product regardless of whether the product has substantial commercial, industrial or non-consumer uses, unless such uses represent the only significant mode of use of the product. "Installation Information" for a User Product means any methods, procedures, authorization keys, or other information required to install and execute modified versions of a covered work in that User Product from a modified version of its Corresponding Source. The information must suffice to ensure that the continued functioning of the modified object code is in no case prevented or interfered with solely because modification has been made. If you convey an object code work under this section in, or with, or specifically for use in, a User Product, and the conveying occurs as part of a transaction in which the right of possession and use of the User Product is transferred to the recipient in perpetuity or for a fixed term (regardless of how the transaction is characterized), the Corresponding Source conveyed under this section must be accompanied by the Installation Information. But this requirement does not apply if neither you nor any third party retains the ability to install modified object code on the User Product (for example, the work has been installed in ROM). The requirement to provide Installation Information does not include a requirement to continue to provide support service, warranty, or updates for a work that has been modified or installed by the recipient, or for the User Product in which it has been modified or installed. Access to a network may be denied when the modification itself materially and adversely affects the operation of the network or violates the rules and protocols for communication across the network. Corresponding Source conveyed, and Installation Information provided, in accord with this section must be in a format that is publicly documented (and with an implementation available to the public in source code form), and must require no special password or key for unpacking, reading or copying. 7. Additional Terms. "Additional permissions" are terms that supplement the terms of this License by making exceptions from one or more of its conditions. Additional permissions that are applicable to the entire Program shall be treated as though they were included in this License, to the extent that they are valid under applicable law. If additional permissions apply only to part of the Program, that part may be used separately under those permissions, but the entire Program remains governed by this License without regard to the additional permissions. When you convey a copy of a covered work, you may at your option remove any additional permissions from that copy, or from any part of it. (Additional permissions may be written to require their own removal in certain cases when you modify the work.) You may place additional permissions on material, added by you to a covered work, for which you have or can give appropriate copyright permission. Notwithstanding any other provision of this License, for material you add to a covered work, you may (if authorized by the copyright holders of that material) supplement the terms of this License with terms: a) Disclaiming warranty or limiting liability differently from the terms of sections 15 and 16 of this License; or b) Requiring preservation of specified reasonable legal notices or author attributions in that material or in the Appropriate Legal Notices displayed by works containing it; or c) Prohibiting misrepresentation of the origin of that material, or requiring that modified versions of such material be marked in reasonable ways as different from the original version; or d) Limiting the use for publicity purposes of names of licensors or authors of the material; or e) Declining to grant rights under trademark law for use of some trade names, trademarks, or service marks; or f) Requiring indemnification of licensors and authors of that material by anyone who conveys the material (or modified versions of it) with contractual assumptions of liability to the recipient, for any liability that these contractual assumptions directly impose on those licensors and authors. All other non-permissive additional terms are considered "further restrictions" within the meaning of section 10. If the Program as you received it, or any part of it, contains a notice stating that it is governed by this License along with a term that is a further restriction, you may remove that term. If a license document contains a further restriction but permits relicensing or conveying under this License, you may add to a covered work material governed by the terms of that license document, provided that the further restriction does not survive such relicensing or conveying. If you add terms to a covered work in accord with this section, you must place, in the relevant source files, a statement of the additional terms that apply to those files, or a notice indicating where to find the applicable terms. Additional terms, permissive or non-permissive, may be stated in the form of a separately written license, or stated as exceptions; the above requirements apply either way. 8. Termination. You may not propagate or modify a covered work except as expressly provided under this License. Any attempt otherwise to propagate or modify it is void, and will automatically terminate your rights under this License (including any patent licenses granted under the third paragraph of section 11). However, if you cease all violation of this License, then your license from a particular copyright holder is reinstated (a) provisionally, unless and until the copyright holder explicitly and finally terminates your license, and (b) permanently, if the copyright holder fails to notify you of the violation by some reasonable means prior to 60 days after the cessation. Moreover, your license from a particular copyright holder is reinstated permanently if the copyright holder notifies you of the violation by some reasonable means, this is the first time you have received notice of violation of this License (for any work) from that copyright holder, and you cure the violation prior to 30 days after your receipt of the notice. Termination of your rights under this section does not terminate the licenses of parties who have received copies or rights from you under this License. If your rights have been terminated and not permanently reinstated, you do not qualify to receive new licenses for the same material under section 10. 9. Acceptance Not Required for Having Copies. You are not required to accept this License in order to receive or run a copy of the Program. Ancillary propagation of a covered work occurring solely as a consequence of using peer-to-peer transmission to receive a copy likewise does not require acceptance. However, nothing other than this License grants you permission to propagate or modify any covered work. These actions infringe copyright if you do not accept this License. Therefore, by modifying or propagating a covered work, you indicate your acceptance of this License to do so. 10. Automatic Licensing of Downstream Recipients. Each time you convey a covered work, the recipient automatically receives a license from the original licensors, to run, modify and propagate that work, subject to this License. You are not responsible for enforcing compliance by third parties with this License. An "entity transaction" is a transaction transferring control of an organization, or substantially all assets of one, or subdividing an organization, or merging organizations. If propagation of a covered work results from an entity transaction, each party to that transaction who receives a copy of the work also receives whatever licenses to the work the party's predecessor in interest had or could give under the previous paragraph, plus a right to possession of the Corresponding Source of the work from the predecessor in interest, if the predecessor has it or can get it with reasonable efforts. You may not impose any further restrictions on the exercise of the rights granted or affirmed under this License. For example, you may not impose a license fee, royalty, or other charge for exercise of rights granted under this License, and you may not initiate litigation (including a cross-claim or counterclaim in a lawsuit) alleging that any patent claim is infringed by making, using, selling, offering for sale, or importing the Program or any portion of it. 11. Patents. A "contributor" is a copyright holder who authorizes use under this License of the Program or a work on which the Program is based. The work thus licensed is called the contributor's "contributor version". A contributor's "essential patent claims" are all patent claims owned or controlled by the contributor, whether already acquired or hereafter acquired, that would be infringed by some manner, permitted by this License, of making, using, or selling its contributor version, but do not include claims that would be infringed only as a consequence of further modification of the contributor version. For purposes of this definition, "control" includes the right to grant patent sublicenses in a manner consistent with the requirements of this License. Each contributor grants you a non-exclusive, worldwide, royalty-free patent license under the contributor's essential patent claims, to make, use, sell, offer for sale, import and otherwise run, modify and propagate the contents of its contributor version. In the following three paragraphs, a "patent license" is any express agreement or commitment, however denominated, not to enforce a patent (such as an express permission to practice a patent or covenant not to sue for patent infringement). To "grant" such a patent license to a party means to make such an agreement or commitment not to enforce a patent against the party. If you convey a covered work, knowingly relying on a patent license, and the Corresponding Source of the work is not available for anyone to copy, free of charge and under the terms of this License, through a publicly available network server or other readily accessible means, then you must either (1) cause the Corresponding Source to be so available, or (2) arrange to deprive yourself of the benefit of the patent license for this particular work, or (3) arrange, in a manner consistent with the requirements of this License, to extend the patent license to downstream recipients. "Knowingly relying" means you have actual knowledge that, but for the patent license, your conveying the covered work in a country, or your recipient's use of the covered work in a country, would infringe one or more identifiable patents in that country that you have reason to believe are valid. If, pursuant to or in connection with a single transaction or arrangement, you convey, or propagate by procuring conveyance of, a covered work, and grant a patent license to some of the parties receiving the covered work authorizing them to use, propagate, modify or convey a specific copy of the covered work, then the patent license you grant is automatically extended to all recipients of the covered work and works based on it. A patent license is "discriminatory" if it does not include within the scope of its coverage, prohibits the exercise of, or is conditioned on the non-exercise of one or more of the rights that are specifically granted under this License. You may not convey a covered work if you are a party to an arrangement with a third party that is in the business of distributing software, under which you make payment to the third party based on the extent of your activity of conveying the work, and under which the third party grants, to any of the parties who would receive the covered work from you, a discriminatory patent license (a) in connection with copies of the covered work conveyed by you (or copies made from those copies), or (b) primarily for and in connection with specific products or compilations that contain the covered work, unless you entered into that arrangement, or that patent license was granted, prior to 28 March 2007. Nothing in this License shall be construed as excluding or limiting any implied license or other defenses to infringement that may otherwise be available to you under applicable patent law. 12. No Surrender of Others' Freedom. If conditions are imposed on you (whether by court order, agreement or otherwise) that contradict the conditions of this License, they do not excuse you from the conditions of this License. If you cannot convey a covered work so as to satisfy simultaneously your obligations under this License and any other pertinent obligations, then as a consequence you may not convey it at all. For example, if you agree to terms that obligate you to collect a royalty for further conveying from those to whom you convey the Program, the only way you could satisfy both those terms and this License would be to refrain entirely from conveying the Program. 13. Use with the GNU Affero General Public License. Notwithstanding any other provision of this License, you have permission to link or combine any covered work with a work licensed under version 3 of the GNU Affero General Public License into a single combined work, and to convey the resulting work. The terms of this License will continue to apply to the part which is the covered work, but the special requirements of the GNU Affero General Public License, section 13, concerning interaction through a network will apply to the combination as such. 14. Revised Versions of this License. The Free Software Foundation may publish revised and/or new versions of the GNU General Public License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns. Each version is given a distinguishing version number. If the Program specifies that a certain numbered version of the GNU General Public License "or any later version" applies to it, you have the option of following the terms and conditions either of that numbered version or of any later version published by the Free Software Foundation. If the Program does not specify a version number of the GNU General Public License, you may choose any version ever published by the Free Software Foundation. If the Program specifies that a proxy can decide which future versions of the GNU General Public License can be used, that proxy's public statement of acceptance of a version permanently authorizes you to choose that version for the Program. Later license versions may give you additional or different permissions. However, no additional obligations are imposed on any author or copyright holder as a result of your choosing to follow a later version. 15. Disclaimer of Warranty. THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION. 16. Limitation of Liability. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. 17. Interpretation of Sections 15 and 16. If the disclaimer of warranty and limitation of liability provided above cannot be given local legal effect according to their terms, reviewing courts shall apply local law that most closely approximates an absolute waiver of all civil liability in connection with the Program, unless a warranty or assumption of liability accompanies a copy of the Program in return for a fee. END OF TERMS AND CONDITIONS How to Apply These Terms to Your New Programs If you develop a new program, and you want it to be of the greatest possible use to the public, the best way to achieve this is to make it free software which everyone can redistribute and change under these terms. To do so, attach the following notices to the program. It is safest to attach them to the start of each source file to most effectively state the exclusion of warranty; and each file should have at least the "copyright" line and a pointer to where the full notice is found. Copyright (C) This program is free software: you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version. This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details. You should have received a copy of the GNU General Public License along with this program. If not, see . Also add information on how to contact you by electronic and paper mail. If the program does terminal interaction, make it output a short notice like this when it starts in an interactive mode: Copyright (C) This program comes with ABSOLUTELY NO WARRANTY; for details type `show w'. This is free software, and you are welcome to redistribute it under certain conditions; type `show c' for details. The hypothetical commands `show w' and `show c' should show the appropriate parts of the General Public License. Of course, your program's commands might be different; for a GUI interface, you would use an "about box". You should also get your employer (if you work as a programmer) or school, if any, to sign a "copyright disclaimer" for the program, if necessary. For more information on this, and how to apply and follow the GNU GPL, see . The GNU General Public License does not permit incorporating your program into proprietary programs. If your program is a subroutine library, you may consider it more useful to permit linking proprietary applications with the library. If this is what you want to do, use the GNU Lesser General Public License instead of this License. But first, please read . PKV0]8) AUTHORSnu[PKV0]I THANKSnu[PKV0]a#READMEnu[PKV0]~|3TODOnu[PKV0]D$~vHH ;ChangeLognu[PKV0]~MrvrvEKNEWSnu[PKn1]|wfKKCOPYINGnu[PKmK