|
From: | Mike Miller |
Subject: | [Octave-bug-tracker] [bug #47480] [octave forge] (io) relies on deprecated octave_config_info |
Date: | Wed, 9 Jan 2019 12:48:02 -0500 (EST) |
User-agent: | Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/71.0.3578.98 Safari/537.36 |
Follow-up Comment #14, bug #47480 (project octave): There is no documented way at the moment for a user to ask Octave if it was supposed to be built with Java support, whether or not the Java runtime is found. I can understand why this might be useful to help a user debug their installation, it tells them whether they need to install Octave again or just need to set JAVA_HOME or install a different JRE or something. If this is specific to Java, because it relies on both compile-time features and run-time environment, what if Octave itself provided a documented Java diagnostic function that could report what is wrong with loading Java? This could take some of the work off of the io package and provide uniform messages for all packages and user code to rely on. If you agree we can move that to a separate wishlist bug. _______________________________________________________ Reply to this item at: <https://savannah.gnu.org/bugs/?47480> _______________________________________________ Message sent via Savannah https://savannah.gnu.org/
[Prev in Thread] | Current Thread | [Next in Thread] |