CERTIFICATION OF COMPLIANCE

Copyright (C) 1996 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.

This certification applies to the Free Software Foundation, Inc.'s official
source code release of the Windows32 API Library Version 0.1.2 as found
at URL, ftp://prep.ai.mit.edu/windows32api-0.1.2.tar.gz.

1. Purpose

The Windows32 API Library Version 0.1.2 is covered by the GNU Library
General Public License Version 2 (LGPL) and as such may be freely
distributed, copied, and modified.  This document is separate from the
LGPL and such is not considered part of nor an addendum to the LGPL.
This document serves to clarify how the LGPL applies to this specific
library and use of its header files.

The LGPL within Section 5 talks about the inclusion of header files, and
the fact that an object file which includes those headers may be considered
a derivative work.  You are encouraged to read the LGPL in completion, it
is the file COPYING.LIB included with the source code for this library, but
here are the relevant paragraphs taken verbatim from the license.

*****

  When a "work that uses the Library" uses material from a header file
that is part of the Library, the object code for the work may be a
derivative work of the Library even though the source code is not.
Whether this is true is especially significant if the work can be
linked without the Library, or if the work is itself a library.  The
threshold for this to be true is not precisely defined by law.

  If such an object file uses only numerical parameters, data
structure layouts and accessors, and small macros and small inline
functions (ten lines or less in length), then the use of the object
file is unrestricted, regardless of whether it is legally a derivative
work.  (Executables containing this object code plus portions of the
Library will still fall under Section 6.)

*****

The second paragraph lays out clear specific guidelines for when the use
of the object file is unrestricted.

The Free Software Foundation realizes that a person may wish to know
whether a library's header files meet these guidelines or not; thus the
Foundation has created this certification documention.  This certification
only applies to the Foundation's release of the library and makes no
claim of any derivative works of the library or even a separate packaging
of the source code files.

2. Certification

This hereby certifies that version 0.1.2 of the Windows32 API Library meets
the guidelines as stated in Section 5 of the LGPL.

The use of an object file that include header files is unrestricted with
regards to the Windows32 API Library; executables containing this object
code plus portions of the Windows32 API Library still fall under the
requirements of Section 6 of the LGPL.  This does not, however, invalidate
any other reason why the use of the object file may be restricted, such
as if the object file includes a header file from another library not
associated with the Windows32 API Library.

3. Verifying

As stated earlier, this certification only applies to the Free Software
Foundation's release of the library; if you receive this library through
another source who has modified the library, then you must obtain a
separate certification from that other source.

If you are unsure whether your source code is the same as the source code
released by the Free Software Foundation, then these are the steps you
should perform to check.

* Obtain the official release at the URL mentioned above.

* Extract the official source code into its own directory.

* Make sure your source code is clean, usually `make distclean'
  from the top level directory should clean out all temporary
  files and return the source code to its distribution state.

* Perform a recursive difference of the two directories; for example

  unknown	- your source code directory
  official	- official release directory

  diff -rc unknown official

* If the diff command reports any differences, then your source code 
  is NOT the same as the official release.  Because this certification
  only applies to header files, if there are no differences in header
  files then this certification still applies.  If there are differences
  in headers file, then this certification does not apply.

If you discover that the header files have changed, then you should either
contact the author of those changes to obtain a certification, or you
can certify the changes yourself by following the instructions in 

4. Certifying your own source code.

The `certhead' program released by the Free Software Foundation is an
automated program which will recursively descend directories and check
that any header files (*.h) meet the guidelines of the LGPL.  Header
files which pass will simply be indicated with "YES"; while files which
do not pass will be indicated with "NO" and details about what part of
the headers do not pass.

