octave-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-bug-tracker] [bug #60993] Environment became unstable and does n


From: anonymous
Subject: [Octave-bug-tracker] [bug #60993] Environment became unstable and does not recognize basic commands
Date: Sat, 31 Jul 2021 17:27:15 -0400 (EDT)
User-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/92.0.4515.107 Safari/537.36 Edg/92.0.902.62

Follow-up Comment #2, bug #60993 (project octave):

Agreed, that it is programmers responsibility to program correctly, although
errors and warnings exist to help of achieving this. 

I think there is a way to handle this issue regardless of OS.   The algorithm
is that each function should do housekeeping when it return value(s). This
housekeeping should check if there are opened file(s), resource or memory
inside that function, and close them if resource handler is not in the list of
return arguments (or class members if that function is a class method).
Warning (or error) should be displayed when fail to close file or resource.
Otherwise, as you said we have resource exhaustion or memory leaks.


    _______________________________________________________

Reply to this item at:

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

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




reply via email to

[Prev in Thread] Current Thread [Next in Thread]