scout 5.7.1 → 5.7.2.pre

data/vendor/json_pure/.gitignore

@@ -1,12 +0,0 @@
-.*.sw[pon]
-coverage
-tags
-pkg
-.nfs.*
-.idea
-java/Json.iml
-Gemfile.lock
-.rvmrc
-*.rbc
-.rbx
-.AppleDouble

data/vendor/json_pure/.travis.yml

@@ -1,20 +0,0 @@
-# Passes arguments to bundle install (http://gembundler.com/man/bundle-install.1.html)
-bundler_args: --binstubs
-
-# Specify which ruby versions you wish to run your tests on, each version will be used
-rvm:
-  - 1.8.7
-  - 1.9.2
-  - 1.9.3
-  - 2.0.0
-  - ree
-  - rbx-18mode
-  - rbx-19mode
-  - jruby-18mode
-  - jruby-19mode
-  - ruby-head
-matrix:
-  allow_failures:
-    - rvm: rbx-18mode
-    - rvm: rbx-19mode
-script: "bundle exec rake"

data/vendor/json_pure/CHANGES

@@ -1,282 +0,0 @@
-2013-05-13 (1.8.0)
-  * Fix https://github.com/flori/json/issues/162 reported by Marc-Andre
-    Lafortune <github_rocks@marc-andre.ca>. Thanks!
-  * Applied patches by Yui NARUSE <naruse@airemix.jp> to suppress warning with
-    -Wchar-subscripts and better validate UTF-8 strings.
-  * Applied patch by ginriki@github to remove unnecessary if.
-  * Add load/dump interface to JSON::GenericObject to make
-        serialize :some_attribute, JSON::GenericObject
-    work in Rails active models for convenient SomeModel#some_attribute.foo.bar
-    access to serialised JSON data.
-2013-02-04 (1.7.7)
-  * Security fix for JSON create_additions default value and
-    JSON::GenericObject. It should not be possible to create additions unless
-    explicitely requested by setting the create_additions argument to true or
-    using the JSON.load/dump interface. If JSON::GenericObject is supposed to
-    be automatically deserialised, this has to be explicitely enabled by
-    setting
-      JSON::GenericObject.json_creatable = true
-    as well.
-  * Remove useless assert in fbuffer implementation.
-  * Apply patch attached to https://github.com/flori/json/issues#issue/155
-    provided by John Shahid <jvshahid@gmail.com>, Thx!
-  * Add license information to rubygems spec data, reported by Jordi Massaguer Pla <jmassaguerpla@suse.de>.
-  * Improve documentation, thx to Zachary Scott <zachary@zacharyscott.net>.
-2012-11-29 (1.7.6)
-  * Add GeneratorState#merge alias for JRuby, fix state accessor methods. Thx to
-   jvshahid@github.
-  * Increase hash likeness of state objects.
-2012-08-17 (1.7.5)
-  * Fix compilation of extension on older rubies.
-2012-07-26 (1.7.4)
-  * Fix compilation problem on AIX, see https://github.com/flori/json/issues/142
-2012-05-12 (1.7.3)
-  * Work around Rubinius encoding issues using iconv for conversion instead.
-2012-05-11 (1.7.2)
-  * Fix some encoding issues, that cause problems for  the pure and the
-    extension variant in jruby 1.9 mode.
-2012-04-28 (1.7.1)
-  * Some small fixes for building
-2012-04-28 (1.7.0)
-  * Add JSON::GenericObject for method access to objects transmitted via JSON.
-2012-04-27 (1.6.7)
-  * Fix possible crash when trying to parse nil value.
-2012-02-11 (1.6.6)
-  * Propagate src encoding to values made from it (fixes 1.9 mode converting
-    everything to ascii-8bit; harmless for 1.8 mode too) (Thomas E. Enebo
-    <tom.enebo@gmail.com>), should fix
-    https://github.com/flori/json/issues#issue/119.
-  * Fix https://github.com/flori/json/issues#issue/124 Thx to Jason Hutchens.
-  * Fix https://github.com/flori/json/issues#issue/117
-2012-01-15 (1.6.5)
-  * Vit Ondruch <v.ondruch@tiscali.cz> reported a bug that shows up when using
-    optimisation under GCC 4.7. Thx to him, Bohuslav Kabrda
-    <bkabrda@redhat.com> and Yui NARUSE <naruse@airemix.jp> for debugging and
-    developing a patch fix.
-2011-12-24 (1.6.4)
-  * Patches that improve speed on JRuby contributed by Charles Oliver Nutter
-    <headius@headius.com>.
-  * Support object_class/array_class with duck typed hash/array.
-2011-12-01 (1.6.3)
-  * Let JSON.load('') return nil as well to make mysql text columns (default to
-    '') work better for serialization.
-2011-11-21 (1.6.2)
-  * Add support for OpenStruct and BigDecimal.
-  * Fix bug when parsing nil in quirks_mode.
-  * Make JSON.dump and JSON.load methods better cooperate with Rails' serialize
-    method. Just use: serialize :value, JSON
-  * Fix bug with time serialization concerning nanoseconds. Thanks for the
-    patch go to Josh Partlow (jpartlow@github).
-  * Improve parsing speed for JSON numbers (integers and floats) in a similar way to
-    what Evan Phoenix <evan@phx.io> suggested in:
-    https://github.com/flori/json/pull/103
-2011-09-18 (1.6.1)
-  * Using -target 1.5 to force Java bits to compile with 1.5.
-2011-09-12 (1.6.0)
-  * Extract utilities (prettifier and GUI-editor) in its own gem json-utils.
-  * Split json/add/core into different files for classes to be serialised.
-2011-08-31 (1.5.4)
-  * Fix memory leak when used from multiple JRuby. (Patch by
-    jfirebaugh@github).
-  * Apply patch by Eric Wong <nocode@yhbt.net> that fixes garbage collection problem
-    reported in https://github.com/flori/json/issues/46.
-  * Add :quirks_mode option to parser and generator.
-  * Add support for Rational and Complex number additions via json/add/complex
-    and json/add/rational requires.
-2011-06-20 (1.5.3)
-  * Alias State#configure method as State#merge to increase duck type synonymy with Hash.
-	* Add as_json methods in json/add/core, so rails can create its json objects
-	  the new way.
-2011-05-11 (1.5.2)
-  * Apply documentation patch by Cory Monty <cory.monty@gmail.com>.
-  * Add gemspecs for json and json_pure.
-  * Fix bug in jruby pretty printing.
-  * Fix bug in object_class and array_class when inheriting from Hash or Array.
-2011-01-24 (1.5.1)
-  * Made rake-compiler build a fat binary gem. This should fix issue
-    https://github.com/flori/json/issues#issue/54.
-2011-01-22 (1.5.0)
-  * Included Java source codes for the Jruby extension made by Daniel Luz
-    <dev@mernen.com>.
-  * Output full exception message of deep_const_get to aid debugging.
-  * Fixed an issue with ruby 1.9 Module#const_defined? method, that was
-    reported by Riley Goodside.
-2010-08-09 (1.4.6)
-  * Fixed oversight reported in http://github.com/flori/json/issues/closed#issue/23,
-    always create a new object from the state prototype.
-  * Made pure and ext api more similar again.
-2010-08-07 (1.4.5)
-  * Manage data structure nesting depth in state object during generation. This
-    should reduce problems with to_json method definіtions that only have one
-    argument.
-  * Some fixes in the state objects and additional tests.
-2010-08-06 (1.4.4)
-  * Fixes build problem for rubinius under OS X, http://github.com/flori/json/issues/closed#issue/25
-  * Fixes crashes described in http://github.com/flori/json/issues/closed#issue/21 and
-    http://github.com/flori/json/issues/closed#issue/23
-2010-05-05 (1.4.3)
-  * Fixed some test assertions, from Ruby r27587 and r27590, patch by nobu.
-  * Fixed issue http://github.com/flori/json/issues/#issue/20 reported by
-    electronicwhisper@github. Thx!
-2010-04-26 (1.4.2)
-  * Applied patch from naruse Yui NARUSE <naruse@airemix.com> to make building with
-    Microsoft Visual C possible again.
-  * Applied patch from devrandom <c1.github@niftybox.net> in order to allow building of
-    json_pure if extensiontask is not present.
-  * Thanks to Dustin Schneider <dustin@stocktwits.com>, who reported a memory
-    leak, which is fixed in this release.
-  * Applied 993f261ccb8f911d2ae57e9db48ec7acd0187283 patch from josh@github.
-2010-04-25 (1.4.1)
-  * Fix for a bug reported by Dan DeLeo <dan@kallistec.com>, caused by T_FIXNUM
-    being different on 32bit/64bit architectures.
-2010-04-23 (1.4.0)
-  * Major speed improvements and building with simplified
-    directory/file-structure.
-  * Extension should at least be comapatible with MRI, YARV and Rubinius.
-2010-04-07 (1.2.4)
-  * Triger const_missing callback to make Rails' dynamic class loading work.
-2010-03-11 (1.2.3)
-  * Added a State#[] method which returns an attribute's value in order to
-    increase duck type compatibility to Hash.
-2010-02-27 (1.2.2)
-  * Made some changes to make the building of the parser/generator compatible
-    to Rubinius.
-2009-11-25 (1.2.1)
-  * Added :symbolize_names option to Parser, which returns symbols instead of
-    strings in object names/keys.
-2009-10-01 (1.2.0)
-  * fast_generate now raises an exeception for nan and infinite floats.
-  * On Ruby 1.8 json supports parsing of UTF-8, UTF-16BE, UTF-16LE, UTF-32BE,
-    and UTF-32LE JSON documents now. Under Ruby 1.9 the M17n conversion
-    functions are used to convert from all supported encodings. ASCII-8BIT
-    encoded strings are handled like all strings under Ruby 1.8 were.
-  * Better documentation
-2009-08-23 (1.1.9)
-  * Added forgotten main doc file extra_rdoc_files.
-2009-08-23 (1.1.8)
-  * Applied a patch by OZAWA Sakuro <sakuro@2238club.org> to make json/pure
-    work in environments that don't provide iconv.
-  * Applied patch by okkez_ in order to fix Ruby Bug #1768:
-      http://redmine.ruby-lang.org/issues/show/1768.
-  * Finally got around to avoid the rather paranoid escaping of ?/ characters
-    in the generator's output. The parsers aren't affected by this change.
-    Thanks to Rich Apodaca <rapodaca@metamolecular.com> for the suggestion.
-2009-06-29 (1.1.7)
-  * Security Fix for JSON::Pure::Parser. A specially designed string could
-    cause catastrophic backtracking in one of the parser's regular expressions
-    in earlier 1.1.x versions. JSON::Ext::Parser isn't affected by this issue.
-    Thanks to Bartosz Blimke <bartosz@new-bamboo.co.uk> for reporting this
-    problem.
-  * This release also uses a less strict ruby version requirement for the
-    creation of the mswin32 native gem.
-2009-05-10 (1.1.6)
-  * No changes. І tested native linux gems in the last release and they don't
-    play well with different ruby versions other than the one the gem was built
-    with. This release is just to bump the version number in order to skip the
-    native gem on rubyforge.
-2009-05-10 (1.1.5)
-  * Started to build gems with rake-compiler gem.
-  * Applied patch object/array class patch from Brian Candler
-    <B.Candler@pobox.com> and fixes.
-2009-04-01 (1.1.4)
-  * Fixed a bug in the creation of serialized generic rails objects reported by
-    Friedrich Graeter <graeter@hydrixos.org>.
-  * Deleted tests/runner.rb, we're using testrb instead.
-  * Editor supports Infinity in numbers now.
-  * Made some changes in order to get the library to compile/run under Ruby
-    1.9.
-  * Improved speed of the code path for the fast_generate method in the pure
-    variant.
-2008-07-10 (1.1.3)
-  * Wesley Beary <monki@geemus.com> reported a bug in json/add/core's DateTime
-    handling: If the nominator and denominator of the offset were divisible by
-    each other Ruby's Rational#to_s returns them as an integer not a fraction
-    with '/'. This caused a ZeroDivisionError during parsing.
-  * Use Date#start and DateTime#start instead of sg method, while
-    remaining backwards compatible.
-  * Supports ragel >= 6.0 now.
-  * Corrected some tests.
-  * Some minor changes.
-2007-11-27 (1.1.2)
-  * Remember default dir (last used directory) in editor.
-  * JSON::Editor.edit method added, the editor can now receive json texts from
-    the clipboard via C-v.
-  * Load json texts from an URL pasted via middle button press.
-  * Added :create_additions option to Parser. This makes it possible to disable
-    the creation of additions by force, in order to treat json texts as data
-    while having additions loaded.
-  * Jacob Maine <jmaine@blurb.com> reported, that JSON(:foo) outputs a JSON
-    object if the rails addition is enabled, which is wrong. It now outputs a
-    JSON string "foo" instead, like suggested by Jacob Maine.
-  * Discovered a bug in the Ruby Bugs Tracker on rubyforge, that was reported
-    by John Evans lgastako@gmail.com. He could produce a crash in the JSON
-    generator by returning something other than a String instance from a
-    to_json method. I now guard against this by doing a rather crude type
-    check, which raises an exception instead of crashing.
-2007-07-06 (1.1.1)
-  * Yui NARUSE <naruse@airemix.com> sent some patches to fix tests for Ruby
-    1.9. I applied them and adapted some of them a bit to run both on 1.8 and
-    1.9.
-  * Introduced a JSON.parse! method without depth checking for people who like
-    danger.
-  * Made generate and pretty_generate methods configurable by an options hash.
-  * Added :allow_nan option to parser and generator in order to handle NaN,
-    Infinity, and -Infinity correctly - if requested. Floats, which aren't numbers,
-    aren't valid JSON according to RFC4627, so by default an exception will be
-    raised if any of these symbols are encountered. Thanks to Andrea Censi
-    <andrea.censi@dis.uniroma1.it> for his hint about this.
-  * Fixed some more tests for Ruby 1.9.
-  * Implemented dump/load interface of Marshal as suggested in ruby-core:11405
-    by murphy <murphy@rubychan.de>.
-  * Implemented the max_nesting feature for generate methods, too.
-  * Added some implementations for ruby core's custom objects for
-    serialisation/deserialisation purposes.
-2007-05-21 (1.1.0)
-  * Implemented max_nesting feature for parser to avoid stack overflows for
-    data from untrusted sources. If you trust the source, you can disable it
-    with the option max_nesting => false.
-  * Piers Cawley <pdcawley@bofh.org.uk> reported a bug, that not every
-    character can be escaped by ?\ as required by RFC4627. There's a
-    contradiction between David Crockford's JSON checker test vectors (in
-    tests/fixtures) and RFC4627, though. I decided to stick to the RFC, because
-    the JSON checker seems to be a bit older than the RFC.
-  * Extended license to Ruby License, which includes the GPL.
-  * Added keyboard shortcuts, and 'Open location' menu item to edit_json.rb.
-2007-05-09 (1.0.4)
-  * Applied a patch from Yui NARUSE <naruse@airemix.com> to make JSON compile
-    under Ruby 1.9. Thank you very much for mailing it to me!
-  * Made binary variants of JSON fail early, instead of falling back to the
-    pure version. This should avoid overshadowing of eventual problems while
-    loading of the binary.
-2007-03-24 (1.0.3)
-  * Improved performance of pure variant a bit.
-  * The ext variant of this release supports the mswin32 platform. Ugh!
-2007-03-24 (1.0.2)
-  * Ext Parser didn't parse 0e0 correctly into 0.0: Fixed!
-2007-03-24 (1.0.1)
-  * Forgot some object files in the build dir. I really like that - not!
-2007-03-24 (1.0.0)
-  * Added C implementations for the JSON generator and a ragel based JSON
-    parser in C.
-  * Much more tests, especially fixtures from json.org.
-  * Further improved conformance to RFC4627.
-2007-02-09 (0.4.3)
-  * Conform more to RFC4627 for JSON: This means JSON strings
-    now always must contain exactly one object "{ ... }" or array "[ ... ]" in
-    order to be parsed without raising an exception. The definition of what
-    constitutes a whitespace is narrower in JSON than in Ruby ([ \t\r\n]), and
-    there are differences in floats and integers (no octals or hexadecimals) as
-    well.
-  * Added aliases generate and pretty_generate of unparse and pretty_unparse.
-  * Fixed a test case.
-  * Catch an Iconv::InvalidEncoding exception, that seems to occur on some Sun
-    boxes with SunOS 5.8, if iconv doesn't support utf16 conversions. This was
-    reported by Andrew R Jackson <andrewj@bcm.tmc.edu>, thanks a bunch!
-2006-08-25 (0.4.2)
-  * Fixed a bug in handling solidi (/-characters), that was reported by
-    Kevin Gilpin <kevin.gilpin@alum.mit.edu>.
-2006-02-06 (0.4.1)
-  * Fixed a bug related to escaping with backslashes. Thanks for the report go
-    to Florian Munz <surf@theflow.de>.
-2005-09-23 (0.4.0)
-  * Initial Rubyforge Version

data/vendor/json_pure/COPYING

@@ -1,58 +0,0 @@
-Ruby is copyrighted free software by Yukihiro Matsumoto <matz@netlab.co.jp>.
-You can redistribute it and/or modify it under either the terms of the GPL
-(see GPL file), or the conditions below:
-
-  1. You may make and give away verbatim copies of the source form of the
-     software without restriction, provided that you duplicate all of the
-     original copyright notices and associated disclaimers.
-
-  2. You may modify your copy of the software in any way, provided that
-     you do at least ONE of the following:
-
-       a) place your modifications in the Public Domain or otherwise
-          make them Freely Available, such as by posting said
-	  modifications to Usenet or an equivalent medium, or by allowing
-	  the author to include your modifications in the software.
-
-       b) use the modified software only within your corporation or
-          organization.
-
-       c) rename any non-standard executables so the names do not conflict
-	  with standard executables, which must also be provided.
-
-       d) make other distribution arrangements with the author.
-
-  3. You may distribute the software in object code or executable
-     form, provided that you do at least ONE of the following:
-
-       a) distribute the executables and library files of the software,
-	  together with instructions (in the manual page or equivalent)
-	  on where to get the original distribution.
-
-       b) accompany the distribution with the machine-readable source of
-	  the software.
-
-       c) give non-standard executables non-standard names, with
-          instructions on where to get the original software distribution.
-
-       d) make other distribution arrangements with the author.
-
-  4. You may modify and include the part of the software into any other
-     software (possibly commercial).  But some files in the distribution
-     are not written by the author, so that they are not under this terms.
-
-     They are gc.c(partly), utils.c(partly), regex.[ch], st.[ch] and some
-     files under the ./missing directory.  See each file for the copying
-     condition.
-
-  5. The scripts and library files supplied as input to or produced as 
-     output from the software do not automatically fall under the
-     copyright of the software, but belong to whomever generated them, 
-     and may be sold commercially, and may be aggregated with this
-     software.
-
-  6. THIS SOFTWARE IS PROVIDED "AS IS" AND WITHOUT ANY EXPRESS OR
-     IMPLIED WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED
-     WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
-     PURPOSE.
-

data/vendor/json_pure/COPYING-json-jruby

@@ -1,57 +0,0 @@
-JSON-JRuby is copyrighted free software by Daniel Luz <mernen at gmail dot com>,
-and is a derivative work of Florian Frank's json library <flori at ping dot de>.
-You can redistribute it and/or modify it under either the terms of the GPL
-version 2 (see the file GPL), or the conditions below:
-
-  1. You may make and give away verbatim copies of the source form of the
-     software without restriction, provided that you duplicate all of the
-     original copyright notices and associated disclaimers.
-
-  2. You may modify your copy of the software in any way, provided that
-     you do at least ONE of the following:
-
-       a) place your modifications in the Public Domain or otherwise
-          make them Freely Available, such as by posting said
-	  modifications to Usenet or an equivalent medium, or by allowing
-	  the author to include your modifications in the software.
-
-       b) use the modified software only within your corporation or
-          organization.
-
-       c) give non-standard binaries non-standard names, with
-          instructions on where to get the original software distribution.
-
-       d) make other distribution arrangements with the author.
-
-  3. You may distribute the software in object code or binary form,
-     provided that you do at least ONE of the following:
-
-       a) distribute the binaries and library files of the software,
-	  together with instructions (in the manual page or equivalent)
-	  on where to get the original distribution.
-
-       b) accompany the distribution with the machine-readable source of
-	  the software.
-
-       c) give non-standard binaries non-standard names, with
-          instructions on where to get the original software distribution.
-
-       d) make other distribution arrangements with the author.
-
-  4. You may modify and include the part of the software into any other
-     software (possibly commercial).  But some files in the distribution
-     are not written by the author, so that they are not under these terms.
-
-     For the list of those files and their copying conditions, see the
-     file LEGAL.
-
-  5. The scripts and library files supplied as input to or produced as 
-     output from the software do not automatically fall under the
-     copyright of the software, but belong to whomever generated them, 
-     and may be sold commercially, and may be aggregated with this
-     software.
-
-  6. THIS SOFTWARE IS PROVIDED "AS IS" AND WITHOUT ANY EXPRESS OR
-     IMPLIED WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED
-     WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
-     PURPOSE.

data/vendor/json_pure/GPL

@@ -1,340 +0,0 @@
-                    GNU GENERAL PUBLIC LICENSE
-                       Version 2, June 1991
-
- Copyright (C) 1989, 1991 Free Software Foundation, Inc.
-                       59 Temple Place, Suite 330, Boston, MA  02111-1307  USA
- Everyone is permitted to copy and distribute verbatim copies
- of this license document, but changing it is not allowed.
-
-                            Preamble
-
-  The licenses for most software are designed to take away your
-freedom to share and change it.  By contrast, the GNU General Public
-License is intended to guarantee your freedom to share and change free
-software--to make sure the software is free for all its users.  This
-General Public License applies to most of the Free Software
-Foundation's software and to any other program whose authors commit to
-using it.  (Some other Free Software Foundation software is covered by
-the GNU Library General Public License instead.)  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
-this service 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 make restrictions that forbid
-anyone to deny you these rights or to ask you to surrender the rights.
-These restrictions translate to certain responsibilities for you if you
-distribute copies of the software, or if you modify it.
-
-  For example, if you distribute copies of such a program, whether
-gratis or for a fee, you must give the recipients all the rights that
-you have.  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.
-
-  We protect your rights with two steps: (1) copyright the software, and
-(2) offer you this license which gives you legal permission to copy,
-distribute and/or modify the software.
-
-  Also, for each author's protection and ours, we want to make certain
-that everyone understands that there is no warranty for this free
-software.  If the software is modified by someone else and passed on, we
-want its recipients to know that what they have is not the original, so
-that any problems introduced by others will not reflect on the original
-authors' reputations.
-
-  Finally, any free program is threatened constantly by software
-patents.  We wish to avoid the danger that redistributors of a free
-program will individually obtain patent licenses, in effect making the
-program proprietary.  To prevent this, we have made it clear that any
-patent must be licensed for everyone's free use or not licensed at all.
-
-  The precise terms and conditions for copying, distribution and
-modification follow.
-
-                    GNU GENERAL PUBLIC LICENSE
-   TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
-
-  0. This License applies to any program or other work which contains
-a notice placed by the copyright holder saying it may be distributed
-under the terms of this General Public License.  The "Program", below,
-refers to any such program or work, and a "work based on the Program"
-means either the Program or any derivative work under copyright law:
-that is to say, a work containing the Program or a portion of it,
-either verbatim or with modifications and/or translated into another
-language.  (Hereinafter, translation is included without limitation in
-the term "modification".)  Each licensee is addressed as "you".
-
-Activities other than copying, distribution and modification are not
-covered by this License; they are outside its scope.  The act of
-running the Program is not restricted, and the output from the Program
-is covered only if its contents constitute a work based on the
-Program (independent of having been made by running the Program).
-Whether that is true depends on what the Program does.
-
-  1. You may copy and distribute 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 and disclaimer of warranty; keep intact all the
-notices that refer to this License and to the absence of any warranty;
-and give any other recipients of the Program a copy of this License
-along with the Program.
-
-You may charge a fee for the physical act of transferring a copy, and
-you may at your option offer warranty protection in exchange for a fee.
-
-  2. You may modify your copy or copies of the Program or any portion
-of it, thus forming a work based on the Program, and copy and
-distribute such modifications or work under the terms of Section 1
-above, provided that you also meet all of these conditions:
-
-    a) You must cause the modified files to carry prominent notices
-    stating that you changed the files and the date of any change.
-
-    b) You must cause any work that you distribute or publish, that in
-    whole or in part contains or is derived from the Program or any
-    part thereof, to be licensed as a whole at no charge to all third
-    parties under the terms of this License.
-
-    c) If the modified program normally reads commands interactively
-    when run, you must cause it, when started running for such
-    interactive use in the most ordinary way, to print or display an
-    announcement including an appropriate copyright notice and a
-    notice that there is no warranty (or else, saying that you provide
-    a warranty) and that users may redistribute the program under
-    these conditions, and telling the user how to view a copy of this
-    License.  (Exception: if the Program itself is interactive but
-    does not normally print such an announcement, your work based on
-    the Program is not required to print an announcement.)
-
-These requirements apply to the modified work as a whole.  If
-identifiable sections of that work are not derived from the Program,
-and can be reasonably considered independent and separate works in
-themselves, then this License, and its terms, do not apply to those
-sections when you distribute them as separate works.  But when you
-distribute the same sections as part of a whole which is a work based
-on the Program, the distribution of the whole must be on the terms of
-this License, whose permissions for other licensees extend to the
-entire whole, and thus to each and every part regardless of who wrote it.
-
-Thus, it is not the intent of this section to claim rights or contest
-your rights to work written entirely by you; rather, the intent is to
-exercise the right to control the distribution of derivative or
-collective works based on the Program.
-
-In addition, mere aggregation of another work not based on the Program
-with the Program (or with a work based on the Program) on a volume of
-a storage or distribution medium does not bring the other work under
-the scope of this License.
-
-  3. You may copy and distribute the Program (or a work based on it,
-under Section 2) in object code or executable form under the terms of
-Sections 1 and 2 above provided that you also do one of the following:
-
-    a) Accompany it with the complete corresponding machine-readable
-    source code, which must be distributed under the terms of Sections
-    1 and 2 above on a medium customarily used for software interchange; or,
-
-    b) Accompany it with a written offer, valid for at least three
-    years, to give any third party, for a charge no more than your
-    cost of physically performing source distribution, a complete
-    machine-readable copy of the corresponding source code, to be
-    distributed under the terms of Sections 1 and 2 above on a medium
-    customarily used for software interchange; or,
-
-    c) Accompany it with the information you received as to the offer
-    to distribute corresponding source code.  (This alternative is
-    allowed only for noncommercial distribution and only if you
-    received the program in object code or executable form with such
-    an offer, in accord with Subsection b above.)
-
-The source code for a work means the preferred form of the work for
-making modifications to it.  For an executable work, complete source
-code means all the source code for all modules it contains, plus any
-associated interface definition files, plus the scripts used to
-control compilation and installation of the executable.  However, as a
-special exception, the source code distributed need not include
-anything that is normally distributed (in either source or binary
-form) with the major components (compiler, kernel, and so on) of the
-operating system on which the executable runs, unless that component
-itself accompanies the executable.
-
-If distribution of executable or object code is made by offering
-access to copy from a designated place, then offering equivalent
-access to copy the source code from the same place counts as
-distribution of the source code, even though third parties are not
-compelled to copy the source along with the object code.
-
-  4. You may not copy, modify, sublicense, or distribute the Program
-except as expressly provided under this License.  Any attempt
-otherwise to copy, modify, sublicense or distribute the Program is
-void, and will automatically terminate your rights under this License.
-However, parties who have received copies, or rights, from you under
-this License will not have their licenses terminated so long as such
-parties remain in full compliance.
-
-  5. You are not required to accept this License, since you have not
-signed it.  However, nothing else grants you permission to modify or
-distribute the Program or its derivative works.  These actions are
-prohibited by law if you do not accept this License.  Therefore, by
-modifying or distributing the Program (or any work based on the
-Program), you indicate your acceptance of this License to do so, and
-all its terms and conditions for copying, distributing or modifying
-the Program or works based on it.
-
-  6. Each time you redistribute the Program (or any work based on the
-Program), the recipient automatically receives a license from the
-original licensor to copy, distribute or modify the Program subject to
-these terms and conditions.  You may not impose any further
-restrictions on the recipients' exercise of the rights granted herein.
-You are not responsible for enforcing compliance by third parties to
-this License.
-
-  7. If, as a consequence of a court judgment or allegation of patent
-infringement or for any other reason (not limited to patent issues),
-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
-distribute so as to satisfy simultaneously your obligations under this
-License and any other pertinent obligations, then as a consequence you
-may not distribute the Program at all.  For example, if a patent
-license would not permit royalty-free redistribution of the Program by
-all those who receive copies directly or indirectly through you, then
-the only way you could satisfy both it and this License would be to
-refrain entirely from distribution of the Program.
-
-If any portion of this section is held invalid or unenforceable under
-any particular circumstance, the balance of the section is intended to
-apply and the section as a whole is intended to apply in other
-circumstances.
-
-It is not the purpose of this section to induce you to infringe any
-patents or other property right claims or to contest validity of any
-such claims; this section has the sole purpose of protecting the
-integrity of the free software distribution system, which is
-implemented by public license practices.  Many people have made
-generous contributions to the wide range of software distributed
-through that system in reliance on consistent application of that
-system; it is up to the author/donor to decide if he or she is willing
-to distribute software through any other system and a licensee cannot
-impose that choice.
-
-This section is intended to make thoroughly clear what is believed to
-be a consequence of the rest of this License.
-
-  8. If the distribution and/or use of the Program is restricted in
-certain countries either by patents or by copyrighted interfaces, the
-original copyright holder who places the Program under this License
-may add an explicit geographical distribution limitation excluding
-those countries, so that distribution is permitted only in or among
-countries not thus excluded.  In such case, this License incorporates
-the limitation as if written in the body of this License.
-
-  9. The Free Software Foundation may publish revised and/or new versions
-of the 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 a version number of this License which applies to it and "any
-later version", you have the option of following the terms and conditions
-either of that version or of any later version published by the Free
-Software Foundation.  If the Program does not specify a version number of
-this License, you may choose any version ever published by the Free Software
-Foundation.
-
-  10. If you wish to incorporate parts of the Program into other free
-programs whose distribution conditions are different, write to the author
-to ask for permission.  For software which is copyrighted by the Free
-Software Foundation, write to the Free Software Foundation; we sometimes
-make exceptions for this.  Our decision will be guided by the two goals
-of preserving the free status of all derivatives of our free software and
-of promoting the sharing and reuse of software generally.
-
-                            NO WARRANTY
-
-  11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, 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.
-
-  12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
-WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR
-REDISTRIBUTE 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.
-
-                     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
-convey the exclusion of warranty; and each file should have at least
-the "copyright" line and a pointer to where the full notice is found.
-
-    <one line to give the program's name and a brief idea of what it does.>
-    Copyright (C) <year>  <name of author>
-
-    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 2 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, write to the Free Software
-    Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA  02111-1307  USA
-
-
-Also add information on how to contact you by electronic and paper mail.
-
-If the program is interactive, make it output a short notice like this
-when it starts in an interactive mode:
-
-    Gnomovision version 69, Copyright (C) year name of author
-    Gnomovision 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, the commands you use may
-be called something other than `show w' and `show c'; they could even be
-mouse-clicks or menu items--whatever suits your program.
-
-You should also get your employer (if you work as a programmer) or your
-school, if any, to sign a "copyright disclaimer" for the program, if
-necessary.  Here is a sample; alter the names:
-
-  Yoyodyne, Inc., hereby disclaims all copyright interest in the program
-  `Gnomovision' (which makes passes at compilers) written by James Hacker.
-
-  <signature of Ty Coon>, 1 April 1989
-  Ty Coon, President of Vice
-
-This 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 Library General
-Public License instead of this License.