octave-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-bug-tracker] [bug #39063] java: restriction on jvm arguments


From: Ernst Reissner
Subject: [Octave-bug-tracker] [bug #39063] java: restriction on jvm arguments
Date: Sun, 26 May 2013 22:31:48 +0000
User-agent: Mozilla/5.0 (X11; Linux i686; rv:7.0.1) Gecko/20100101 Firefox/7.0.1

Follow-up Comment #7, bug #39063 (project octave):

because of the unboxing problem i went back to old java-1.2.9 
For this, i checked options -ea and -esa. 
Implicitly also -da and -dsa and it worked well. 

I am not sure whether you are interested in a check for java-1.2.9. 
If not, i wait until the (un)boxing problem disappears. 
I read the tests and am willing to contribute. 

I am also not sure whether you like my fix: 
For now I just removed any check. 
I think, one should be allowed to use all possible for the JVM. 
Since there is an option file java.opts dedicated for octave integration, 
one can put into this file the options appropriate for octave. 
These may differ from options for standalone java applications. 
I think one has to place a remark on the danger in the docu 
but let the user experiment and give feed back. 
It seems to be no good to just ignore options. 

But if you want, we can also test on standard options 
and -X-options. 
But there are lots and as i said before: 
-X... is nonstandard (except -X alone) and -XX... is even unstable 


What do you think? 

    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?39063>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/




reply via email to

[Prev in Thread] Current Thread [Next in Thread]