Defining class methods in the "deeper levels" of a class

1 view (last 30 days)
Philip M
Philip M on 27 Nov 2020
Edited: Philip M on 28 Nov 2020
I would like to be able to define class A in such a way that the command A=A.B.Method will be able to modify properties A.PropA and A.B.PropB. The closest I've gotten is by defining B2 as it's own class, and defining a property of A as "B=B2", but I have to use the command A.B=A.B.Method, and I'm not able to modify properties of A. It seems like I may be able to accomplish this or something similar using superclasses and/or object handles or maybe anonymous function handles, but I'm new to defining MATLAB classes and to OOP in general so I can't quite figure it out.

Answers (1)

Jeff Miller
Jeff Miller on 27 Nov 2020
A toy example might be needed to make it clearer what you are after, but I guess you want a class A which has as two of its properties a variable PropA and an object B.
If that's right, then it wouldn't be good OOP to have a call to B modify PropA, even if that is possible.
It would be better to make PropA a function (of A) that simply calls the function of B (call it "GiveMePropA") that returns the value you want PropA to have. If GiveMePropA is expensive to compute, you might just have A call it whenever needed and store its value.
Philip M
Philip M on 28 Nov 2020
I was thinking the Ledger would be a .m file, but what I'm ultimately trying to accomplish is for all the budgeting and financial information to be contained in a single object. The Budget object will be the top of the heiarchy though, so maybe Ledger would be a property of that? I'm not sure, I'll have to put some thought into it. I'm also doing this as practice for learning how to use OOP in MATLAB, so I'll probably just try some different things and see what I like best.
EDIT: Actually, I guess the root of what I was trying to do was to organize the methods of Budget a little better. So instead of having methods Budget.NewBill, Budget.ModifyBill, Budget.NewLoan, Budget.NewLoanStatement, etc. I would rather group those methods and instead call them using Budget.Bill.New, Budget.Bill.Modify, Budget.Loan.New, Budget.Loan.NewStatement, etc. Bill and Loan don't necessarily have to be their own classes, that just seemed like the most practical way to do it at first. I would actually prefer to only define one class, Budget, if possible.

Sign in to comment.

Community Treasure Hunt

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

Start Hunting!