[Octave-bug-tracker] [bug #46281] newly defined private functions are inaccessible until restart of octave session

[Tasos Papastylianou]

Follow-up Comment #5, bug #46281 (project octave):

Hi Doug,

I have confirmed this bug on three different machines (one laptop and two
desktops) using
* Octave 4.0.0 stable on Windows (installed via binary)
* Octave 4.0.0 stable on Linux (compiled), and
* Octave dev version (4.1.0+) on Linux (compiled, obviously)
* Both the GUI and CLI versions on all of the above

In our irc chat where we briefly discussed this, JWE confirmed it
independently, but Mike (mtmx) had the same experience as you and Pantxo.

So, yes, it seems this may not be consistent across builds ... unless you're
doing something slightly different to what I'm doing. Are you sure there was
no private folder before starting the octave session?

    _______________________________________________________

Reply to this item at:

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

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