|
From: | John W. Eaton |
Subject: | [Octave-bug-tracker] [bug #53844] handle class: delete destructor method cannot access class properties |
Date: | Mon, 14 May 2018 14:53:44 -0400 (EDT) |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Firefox/52.0 |
Update of bug #53844 (project octave): Status: In Progress => Ready For Test _______________________________________________________ Follow-up Comment #11: I pushed the following changeset on stable: http://hg.savannah.gnu.org/hgweb/octave/rev/97f1d513aaf6 This change (and also http://hg.savannah.gnu.org/hgweb/octave/rev/0548e32e6b27) modifies a public interface so it might not be possible for some .oct files compiled for 4.4.0 to work with newer 4.4.x releases, or for .oct files compiled for a future 4.4.x release to work with 4.4.0. But as I understand it, that would be limited to code that actually uses these fairly obscure interfaces. Should we care about that? If so, then I'm willing to defer this change until version 5, but then I think we should just completely disable automatically calling the delete method for classdef handle objects in any future 4.4.x releases. Comments? _______________________________________________________ Reply to this item at: <http://savannah.gnu.org/bugs/?53844> _______________________________________________ Message sent via Savannah https://savannah.gnu.org/
[Prev in Thread] | Current Thread | [Next in Thread] |