[libinline-java-perl] 170/398: Doc changes

[Jonas Smedegaard]

This is an automated email from the git hooks/post-receive script.

js pushed a commit to tag 0.55
in repository libinline-java-perl.

commit 1ebf4e5e7248134c6006a03ee87b2fc83e285c92
Author: patrick_leb <>
Date:   Mon Feb 4 20:58:37 2002 +0000

    Doc changes
---
 CHANGES    |  8 ++++++++
 README     |  2 +-
 README.JNI | 54 ++++++++++++++++++++----------------------------------
 3 files changed, 29 insertions(+), 35 deletions(-)

diff --git a/CHANGES b/CHANGES
index 798a76d..5b8bc2c 100644
--- a/CHANGES
+++ b/CHANGES
@@ -1,6 +1,14 @@
 Revision history for Perl extension Inline::Java
 ------------------------------------------------
 
+0.31  Mon Feb  4 15:45:06 EDT 2002
+    - Exception handling (Perl can 'catch' Java exceptions)
+    - Callbacks to Perl from Java
+    - More complete test suite
+    - Improved documentation and related examples
+    - Improved installation script and directions
+    - Other minor bug fixes
+
 0.30  Mon Sep 17 15:45:06 EDT 2001
     - JVM server is now multi-threaded
     - Added 'SHARED_JVM' option for mod_perl support
diff --git a/README b/README
index 811a2f1..31571b1 100644
--- a/README
+++ b/README
@@ -128,4 +128,4 @@ Send email to inline-subscribe at perl.org to subscribe.
 
 Please send questions and comments to "Patrick LeBoutillier" <patl at cpan.org>
 
-Copyright (c) 2001, Patrick LeBoutillier. All Rights Reserved.  
+Copyright (c) 2001-2002, Patrick LeBoutillier. All Rights Reserved.  
diff --git a/README.JNI b/README.JNI
index 2e7c4d2..1b58c4e 100644
--- a/README.JNI
+++ b/README.JNI
@@ -1,17 +1,16 @@
 JNI (JAVA NATIVE INTERFACE) EXTENSION
 -------------------------------------
-
 Inline::Java now provides a JNI extension that allows you to load the Java 
 virtual machine as shared object instead of running it as a separate process. 
 
 
 PLATFORM AVAILABILITY
 ---------------------
-
 The JNI extension is available on all supported platforms.
 
 The extension builds properly on all platform, but problems can occur when
-running it or tweaking maybe necessary on certain platforms.
+running it or tweaking maybe necessary on certain platforms. All help
+is welcome if anyone out there is a JNI expert.
 
 Note: Make sure the directories listed at the end of the installation
 procedure are included in your LD_LIBRARY_PATH (PATH on Win32) environment
@@ -36,47 +35,35 @@ can occur when the process ends. This issue seems to be related to the
 main thread waiting for other threads to terminate.
 
 Java 2 SDK 1.3.1:
-	The JNI extension runs without problems, provided that you add
-<Java 2 SDK installation path>/jre/lib/<arch>/native_threads/libhpi.so
-to your LD_PRELOAD environment variable.
+	The JNI extension runs mostly without problems, provided that you 
+add <Java 2 SDK installation path>/jre/lib/<arch>/native_threads/libhpi.so
+to your LD_PRELOAD environment variable. Some thread related errors have
+been seen on script startup.
 
 
 SOLARIS
 -------
-The JNI extension requires Perl to be built following specific instructions
-in order to run properly on Solaris. Here's what you have to do:
-
-- Make sure all the patches required by your Java 2 SDK are installed on 
-  your system.
-- Rebuild Perl:
-  - Configure Perl
-	- At the end of the Perl configuration, you will be asked if you want 
-      to edit the config.sh file. Say 'yes' and look for the following lines:
-
-      libs='...'
-         Change this to:
-           libs='-lthread ...'
+Java 2 SDK 1.2.2:
+	The JNI extension has been run successfully on Solaris, provided 
+that you add 
+<Java 2 SDK installation path>/jre/lib/<arch>/libmonitor_v8.so
+to your LD_PRELOAD environment variable. Some thread related errors have
+been seen on script startup.
 
-      usemymalloc='...'
-         Change this to:
-           usemymalloc='n'
+Java 2 SDK 1.3.1:
+	The JNI extension has been run successfully on Solaris, provided that 
+you add /lib/libthread.so and
+<Java 2 SDK installation path>/jre/lib/<arch>/native_threads/libhpi.so
+to your LD_PRELOAD environment variable. Some thread related errors have
+been seen on script startup.
 
-  - make
-  - make test 
-    - Note: On my setup, 'make test' failed one test: pragma/warnings #179.
-      But when I followed the instructions:
-        ### Since most tests were successful, you have a good chance to
-        ### get information with better granularity by running
-        ###     ./perl harness 
-        ### in directory ./t.
-      all tests where successful.
 
-Then use this Perl version to build and run Inline::Java.
+Note: These results where achieved with Perl 5.6.1 complied with gcc 
+and using the native malloc.
 
 
 RUNNING Inline::Java WITH THE JNI EXTENSION
 -------------------------------------------
-
 To run Inline::Java with the JNI extension, do one of the following:
 
    - set the JNI configuration option to 1
@@ -88,7 +75,6 @@ PERL_INLINE_JAVA_JNI environment variable
 
 USING THE 'SHARED_JVM' MODE
 ---------------------------
-
 Inline::Java 0.30 introduced a 'SHARED_JVM' mode that allows many clients 
 to connect to the same Inline::Java Java server. The 'SHARED_JVM' mode is 
 meant to be used with forking processes such as Apache with mod_perl. The 

-- 
Alioth's /usr/local/bin/git-commit-notice on /srv/git.debian.org/git/pkg-perl/packages/libinline-java-perl.git