[Octave-bug-tracker] [bug #58811] [octave forge] (parallel) parcellfun modifies load path

[Olaf Till]

Follow-up Comment #1, bug #58811 (project octave):

There were reasons to change parcellfun to use newly started Octave instances.
Any global variables for parallel Octave instances can only (reasonably) be
set in Octaves startup file. This includes system globals like the set path.
So actually parcellfun doesn't modify the path but it doesn't see
modifications.

While I think that for globals set with 'global' in arbitrary user scripts it
is probably reasonable to use variables closed into anonymous functions
instead, system globals like the path should probably be honoured by the
parallel Octave instances. So I put this on my TODO-list.

You mentioned that .octaverc is executed if parcellfun is called. This should
only happen if you call parcellfun for the first time or if you call it with a
higher number of parallel instances than ever used before in the same Octave
session (except if parcellfun_set_nproc was called to reduce the number of
existing parallel instances).

    _______________________________________________________

Reply to this item at:

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

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