[Octave-bug-tracker] [bug #60993] Environment became unstable and does not recognize basic commands

[Markus Mützel]

Update of bug #60993 (project octave):

                  Status:                    None => Wont Fix               
             Open/Closed:                    Open => Closed                 

    _______________________________________________________

Follow-up Comment #4:

A user might have a good reason to leave a file handle open on exiting a
function.
If Octave would close those handles automagically that would be very
surprising (to me at least).

If you are worried about that, you could write a wrapper that checks how many
files are already open before opening a new one. That could look similar to
this:

function [varargout] = fopen_check (varargin)
max_num_open_files = 100;

if (numel (fopen ('all')) > max_num_open_files)
  ## do something...
  ## e.g. emit a warning or an error, or close all open files and continue if
you think you can safely do that
endif

[varargout{1:nargout}] = fopen (varargin{:});

endfunction


Other than that, I often use a construct like the following to make sure that
open file handles are closed when I know they shouldn't leave the scope of the
current function:

fid = fopen ('t.tst', 'w');
fid_guard = onCleanup (@() fclose(fid));


Or `unwind_protect` blocks.

Anyway, closing handles is the responsibility of the user. There are multiple
ways to do that in Octave.

Closing report as won't fix.


    _______________________________________________________

Reply to this item at:

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

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