[Octave-bug-tracker] [bug #47480] [octave forge] (io) relies on deprecated octave_config_info

[Mike Miller]

Follow-up Comment #19, bug #47480 (project octave):

Yeah, the point that Carnë made and I agree with is that 'javachk' can become
that function that acts as a central diagnostic point for users and packages
to query Octave whether Java support is enabled, whether a JVM can be started,
and further whether various JRE features are present.

See bug #55429 for improving 'javachk', maybe in time for Octave 6, and in the
meantime the io package can continue relying on '__have_feature__' and
'__octave_config_info__' internal functions with the understanding that they
are internal and not guaranteed to be stable from version to version now.

    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?47480>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/