[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #51824] octave integration into java
From: |
Andrew Janke |
Subject: |
[Octave-bug-tracker] [bug #51824] octave integration into java |
Date: |
Thu, 19 Jul 2018 05:07:39 -0400 (EDT) |
User-agent: |
Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/67.0.3396.99 Safari/537.36 |
Follow-up Comment #6, bug #51824 (project octave):
FWIW, this is a pretty big project. It sounds like you're asking for
functionality similar to the Matlab Compiler SDK's
<https://www.mathworks.com/products/matlab-compiler-sdk.html> Java support
(formerly known as Matlab Builder JA). This basically means taking the
embeddable version of Octave, wrapping it in a Java class library, and
providing a tool to generate Java class wrappers for user-supplied M-code
entry points. That would require formalizing the parts of octave.jar that
allow dispatching M-code calls from Java code.
I'm not saying it's not worth doing; just noting that it would take a lot of
work.
> Note that matlab is integrated in java as it is written in java.
Only the GUI parts of Matlab and some support libraries are written in Java.
The core of Matlab is a C/C++/Fortran application, like Octave is. The Matlab
Compiler SDK's Java support is a separate wrapper layer on top of the "native"
Matlab application/library. There's synergy in the GUI bits, but that's it.
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?51824>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [Octave-bug-tracker] [bug #51824] octave integration into java,
Andrew Janke <=