[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #55887] Edit changes to classdef object are se
From: |
Rik |
Subject: |
[Octave-bug-tracker] [bug #55887] Edit changes to classdef object are seen(executed) after saving file and re-initializiing the object |
Date: |
Tue, 14 Jan 2020 12:11:12 -0500 (EST) |
User-agent: |
Mozilla/5.0 (Windows NT 10.0; WOW64; Trident/7.0; rv:11.0) like Gecko |
Follow-up Comment #9, bug #55887 (project octave):
I think Octave does the reasonable thing in Octave 6.1. For this code
t1 = testprop (); # create instance of testprop class with test = 0
%% Modify testprop.m so that property test has value = 2
t2 = testprop (); # create second instance of testprop class
t1.test
ans = 0
t2.test
ans = 2
In other words, existing objects are left alone but newly created ones use the
most up-to-date definition.
But, if you want to see WTF! Matlab behavior, visit
https://www.mathworks.com/help/matlab/matlab_oop/modifying-and-reloading-classes.html.
In Matlab, changing the class definition automatically updates all
instantiated objects to reflect the new definition. Thus, if you happen to
have the same classname in different directories then changing the path or
using 'cd' can completely re-instantiate all of your objects.
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?55887>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/