清空筛选条件
清空筛选条件

assigning to object variables from within-object functions

11 次查看（过去 30 天）
Michel du Montmorency
编辑： Luke Perry 2019-7-3
Can anyone explain me the following code, please?
myObj = myClass() ;
newObj = myObj.Increment() ;
disp myObj.Value
disp newObj.Value
myClass is defined as follows:
classdef myClass
properties
Value
end
methods
function self = myClass(self)
self.Value = 5 ;
end
function self = Increment(self)
self.Value = self.Value + 1 ;
end
end
end
Here myObj.Value is always 5, and it is not incremented to 6. In all the other languages I know, there is no need to explicitely write
newObj = oldObj.Function()
in order to make actions of .Function effective on the object itself. Is MATLAB working in that way, or there is something I am missing?
Thank you all,
Mike

请先登录，再回答此问题。

采纳的回答

David Young
David Young 2015-7-6
MATLAB always makes a copy when you assign an object, or pass an object to a function. Here's another example of the same thing, but with a simple array:
a = [1 2 3];
b = a;
b(2) = 99;
disp(a)
which prints
1 2 3
- that is, a has not changed. In just the same way, myObj has been copied and not changed in your code. In general, to change the value of an element of an array or a property of an object, the name of the array or object must appear on the left side of an assignment.
Although this is different to some languages, it's an enormously valuable aspect of MATLAB, and must have saved vast amounts of programmer time over the years. It's consistent, and it entirely avoids a significant class of bugs.
This sounds inefficient, but it isn't - the copy is only made when it's actually necessary.
You can override the default and have the behaviour you are used to by declaring your class to be a handle class. For consistency with the rest of the language this is best avoided, but there are situations where a handle class is called for. For more details see this part of the documentation.

更多回答（1 个）

Brendan Hamm
Brendan Hamm 2015-7-6
编辑：Brendan Hamm 2015-7-6
If you want to have your original object updated you should make your class a handle class:
classdef myClass < handle
properties
Value
end
methods
function self = myClass()
self.Value = 5 ;
end
function Increment(self)
self.Value = self.Value + 1 ;
end
end
end
By default MATLAB is using a pass by value behavior, so you are passing in your object as an argument to a method, but getting back a different object. Handle classes are more akin to classes in other languages and have a pass by reference behavior.
mc = myClass
mc.Increment
mc.Value
ans =
6
  2 个评论
Luke Perry
Luke Perry 2019-7-3
编辑：Luke Perry 2019-7-3
Thank you Brendan. This was very helpful. However, is there any reason for creating another instance of the object and passing it back through?
From what I understand of MATLAB, due to problems in debugging, it is not good to set an object equal to itself such as the following:
myclass=New_Class();
myclass=myclass.SetColor('yellow');
myclasscolor=myclass.GetColor();
where the class is defined below:
classdef New_Class
properties (Access = protected)
color;
end
methods (Access = public)
function obj = New_Class(obj)
obj.color='';
end
end
methods
function obj = SetColor(obj,color)
obj.color=color;
end
function color = GetColor(obj)
color=obj.color;
end
end
end
Why then would the default class be encouraged to act this way? I should be able to just do:
myclass=New_Class();
myclass.SetColor('yellow');
myclasscolor=myclass.GetColor();
Otherwise this seems like a poor way of going about Object-Oriented Programming.

请先登录，再进行评论。

类别

在 Help Center 和 File Exchange 中查找有关 Graphics Object Programming 的更多信息

标签

Community Treasure Hunt

Find the treasures in MATLAB Central and discover how the community can help you!

Start Hunting!

Translated by