[Octave-patch-tracker] [patch #10366] Same destructor order for octave_value:s in frame in std::vector for libstdc++ and libc++

[Petter T.]

Follow-up Comment #2, patch #10366 (project octave):

>From the point of view of the VM it does not matter. It does the libstdc++
order (first to last element of the variables) and does not use the code
effected by the patch.

I guess the destructor execution order matter if a user put side effects in a
classdef dtor? I guess the specific order is not that important, but it might
be confusing of different builds of Octave of the same version are not
deterministic in their execution?

I think I'll do a patch an alternative patch for the test that accepts any
dtor order anyways.


    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/patch/?10366>

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