resetting the path causes java_invoke to fail

[John W. Eaton]

On  3-Jun-2008, Richard Bovey wrote:

| 
| Resetting the octave search path causes java_invoke() to fail on exit().
| Example session below.
| 
| I'm using Windows XP
| OCTAVE_VERSION = 3.0.1
| 
| My aim is to be able to make additions to the path, then later on to restore
| the path to its previous state.
| 
| Regards,
| Richard
| 
| ------------------
| 
| >> OCTAVE_VERSION
| ans = 3.0.1
| >> a = path();
| >> path(a);

If there is nothing between these two lines, then I think the path
should not change.  Does it?

| >> exit
| error: unable to start Java VM in C:\Program
| Files\Java\jre1.6.0_03\bin\client\jvm.dll
| error: in
| D:\Applications\Octave\share\octave\packages\jhandles-0.3.1\__get_object__.m
| near line 20, column 7:
| 
| >>> obj = java_invoke ('org.octave.graphics.HandleObject',
| >>> 'getHandleObject', handle);
| 
| keyboard: stopped in
| D:\Applications\Octave\share\octave\packages\jhandles-0.3.1\__get_object__.m
| at line 20

If the path commands above don't actually change anything, then
perhaps this is a problem with initialization that happens in the
jhandles PKG_ADD file?  I don't know whether it even has one as I
don't have a Windows system on which to try to duplicate this problem,
but that's where I would start looking for problems.

jwe