@(#)README	1.3 97/12/23

__________
Disclaimer

    This is a heart beat test for the old native method interface (Old
    NMI). The presence of this test does not in any way imply that the
    Old NMI is supported, or that it will be compatible across
    releases of the Java Virtual Machine. If you have any native
    methods that use the Old NMI, you should migrate them to JNI
    *now* -- JNI is *the* standard for writing native methods. HotSpot
    and other next generation technologies will not, and can not,
    support this Old NMI.

_______
Purpose

    This test checks that each function historically considered to be
    part of the Old NMI is in fact exported by the runtime and is
    available to native method code.  It tests each of these functions
    for basic operation, but does not test each exhaustively or in
    such a way as to ensure compatibility of these functions across
    releases or across platforms for a given release.  As part of the
    test cycle the test code itself is compiled, which checks for the
    simple existence of the include directory supporting the Old NMI.

_____________
Solaris Usage

    At your command prompt:

	$ gnumake run


___________
Win32 Usage

    At your command prompt

	C:\> nmake run

______________________________
Testing an Alternative Release

    If you want to test a JDK installed somewhere else, use:

	$ gnumake JDK=/usr/local/java/jdk1.1.5/solaris VERSION=1.1 run
	C:\> nmake JDK=c:/jdk1.1.5 VERSION=1.1 run

    The version string can be one of "1.2" or "1.1" and this
    distinction is required because of the location of the header
    files is different, and the VM dll has been renamed. The default
    version is 1.2.

____________________
Interpreting Results

    This is a "no news is good news" test. If it runs to completion
    and the exit status is 0, then you should be okay. However if the
    compiler prints any warnings, or any such things, take a closer
    look.

____
TODO

    Currently, this tests only for functionality. There is no test to
    make sure the transitive closure of header files is installed.

    Since Win32 and Solaris intermediate files get created in the same
    directory, you will have to "clean" in the platform you did a
    build before you can run the test on the other platform. This can
    be quite annoying if you are debugging this test.
