[Octave-bug-tracker] [bug #59192] unwind_protect objects should be replaced with lighter weight alternatives

[John W. Eaton]

Follow-up Comment #8, bug #59192 (project octave):

I started looking at replacing calls to frame.protect_var with
unwind_protect_var<T> objects because I thought that it might be possible to
do most of them fairly easily.  But I quickly discovered (after looking at
just one file!) that there are likely to be many cases that will need some
thought.

I still consider this to be a good change to make but would recommend doing
this job carefully over time rather than trying to do it quickly or
semi-automatically.

It might also be nice to have variadic templates that would allow something
like


unwind_protect_vars<T1, T2, ...> upv1 (var1, var2, ...);

unwind_protect_vars_with_vals<T1, T2, ...>
  upv2 (var1, new_val1, var2, new_val2, ...);



    _______________________________________________________

Reply to this item at:

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

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