Modify attributes of inherited property

8 views (last 30 days)
I defined a subclass which inherits a built-in class (mechss) and extends it with some additional properties and methods. Because of my additional properties, the terminology becomes somewhat confusing and I would like to change the property names of the superclass. For example, I would like to change the property C to be called L.
As far as I understand, this is not possible, but I cán define the new property L and relate it to C using get and set methods. This leaves me with two identical properties however, and I would like to hide C and make its access protected.
Is something like this possible?

Accepted Answer

Matt J
Matt J on 2 Nov 2021
Edited: Matt J on 2 Nov 2021
Not directly, but you can overload the display() method, customizing it so that C is never displayed at the command line. Similarly, you can customize subsref() and subsasgn() so that dot indexing outside the class does not allow access to C.

Sign in to comment.

More Answers (1)

Sean de Wolski
Sean de Wolski on 2 Nov 2021
Edited: Sean de Wolski on 2 Nov 2021
You could instead author your own class that passes through to a mechss object it stores as a private property. Then you can call the properties whatever you want.
Luuk Poort
Luuk Poort on 3 Nov 2021
Thank you for both of your input.
So, option 1 is to inherit the mechss class and overload the subsref and subsasgn methods to access the inherited properties with any name I would like, e.g. C can be obtained by .L, while inherited methods can be accessed both with dot notation or function notation.
With option 2, my class is not a subclass, but stores the mechss object as a private property. This is likely faster and more robust to future changes in built-in code. Methods of mechss can be accessed with dot notation by overloading the dot-indexing to be forwarded to the mechss object. To enable function notation, I need to define a new method for each method of mechss to forward it to the mechss object.
I hope I am correct with this and I will test what works out best for me. Unfortunately I cannot accept two answers.
Regarding the naming confusion: I would like object properties to match terminology in my field and in my own documentation to avoid confusion with users, when I will share my implementation in the future.

Sign in to comment.


Find more on Methods in Help Center and File Exchange





Community Treasure Hunt

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

Start Hunting!