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

[Mike Miller]

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

> But I don't see how that can be done w/o some built-in function

No one is suggesting to do away with internal built in functions completely.
The point is to expose the documented interfaces that are useful for you to
use.

Obviously 'which.m' doesn't work without the '__which__' built in function.
But you are not supposed to call '__which__' directly, its interface is not
documented and not expected to be stable across multiple versions of Octave.
You are obviously *able* to call it, but that doesn't mean you *should* call
it in code that you expect to work across different Octave environments. That
is the distinction that this bug report is about. To stop using internal
functions that you shouldn't be using and identify what replacements, if any,
that Octave needs to add to its public interface to fill in the gaps.

    _______________________________________________________

Reply to this item at:

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

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