One of the exercises in a previous paper examines the possible benefits of developing one get and one set instead of a get and set pair for every public variable. That was before the implementations of subsref and subsasgn. Since subsref and subsasgn provide such an elegant, natural interface, perhaps there is no longer a need for get or set. There are still benefits, but it seems the most compelling reasons were stolen away by subsref and subsasgn. This paper examines some of the benefits and define implementations for get and set that add quite a lot of flexibility. The functions get and set complete the membership roles for the group of eight.

Chapter Contents:

• 8.1 Arguments for the Member Functions get and set
• 8.1.1 For Developers
• 8.1.2 For Clients
• 8.1.3 Tab Completion
• 8.2 Code Development
• 8.2.1 Implementing get and set
• 8.2.2 Initial get.m
• 8.2.3 Initial set.m
• 8.3 The Test Drive
• 8.4 Summary
• 8.5 Independent Investigations

Inspec keywords: object-oriented programming

Other keywords: Matlab; public variable; subsref; get.m; set.m; subsasgn; set development; membership role; get development

Subjects: Object-oriented programming