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

[Philip Nienhuis]

Update of bug #39063 (project octave):

                Category:    Octave Forge Package => Libraries              
                  Status:                    None => Need Info              

    _______________________________________________________

Follow-up Comment #1:

Don't mix up (the Java package in) Octave-Forge and the newly built-in Java
support in core Octave.

Would you have any idea whether Matlab also allows other options than -D and
-X ?  Reading up a bit in e.g., "Undocumented Matlab" (see google) I see no
mention of other flags than -X and -D (save vfprint and abort)
Which is not to say that Octave should be limited to only what ML can, of
course :-)

Note that there may be good reasons that only -X and -D flags are accepted.
One I can think of is that Octave's Java (OF package or built-in) should run
with many JRE (read: JVM) versions which simply may not all accept the same
set of flags; -X and -D seem to constitute the most common subset.
Have you tried to comment out the "offending" lines, rebuild Octave (or
reinstall the patched Java package) and see if -ea and -esa etc. work OK w/o
crashing Octave sooner or later?

BTW Can you explain exactly why stand-alone Java programs and Java stuff run
from within Octave should behave identically? 
I obviously have some intuitive notion of the underlying principle, but
presently I fail to see practical benefits.

("category" adapted to "libraries" as OF Java will probably not receive much
more maintenance)


    _______________________________________________________

Reply to this item at:

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

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