Timeline for Before OOP, were data structure members left public?
Current License: CC BY-SA 4.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 20, 2018 at 18:19 | comment | added | T.E.D. | @David - That was the Ada community's argument for years during the Ada 95 era. I believe they finally gave in and proved their own argument by allowing object.method() as an alternative form for method(object, ...) for people who just couldn't make the conceptual leap. | |
| Jul 20, 2018 at 15:07 | comment | added | David | Also, AFAIK most OO languages work the same way under the hood, i.e. myWidget.getFoo() is really implemented as getFoo(myWidget). The object.method() invocation is just syntactic sugar. Important IMHO -- see Meyer's Principle of Uniform Access / Reference -- but still just syntactic sugar. | |
| Jul 20, 2018 at 15:04 | comment | added | David | I spent quite a bit of time working in Ada. Selective hiding (of part of a data type) was something we did all the time; in the containing package, you'd define the type itself as private or limited private; the package interface would expose public functions/procedures to get and/or set internal fields. Those routines would of course need to take a parameter of the private type. I did not then and do not now consider this difficult. | |
| S Jul 20, 2018 at 13:26 | history | suggested | Peter Mortensen | CC BY-SA 4.0 | Copy edited (e.g. ref. <https://en.wikipedia.org/wiki/The_Mythical_Man-Month>). [(its = possessive, it's = "it is" or "it has". See for example <http://www.wikihow.com/Use-Its-and-It%27s>.) |
| Jul 20, 2018 at 4:40 | review | Suggested edits | |||
| S Jul 20, 2018 at 13:26 | |||||
| Jul 19, 2018 at 18:48 | history | edited | T.E.D. | CC BY-SA 4.0 | deleted 35 characters in body |
| Jul 19, 2018 at 18:40 | history | edited | T.E.D. | CC BY-SA 4.0 | added 249 characters in body |
| Jul 19, 2018 at 18:34 | history | answered | T.E.D. | CC BY-SA 4.0 |