[Main Page]

Encapsulation

(Difference between revisions)

Main Page | Recent changes | View source | Page history | Log in / create account |

Printable version | Disclaimers | Privacy policy | Current revision

Current revision (19:25, 16 May 2005) (edit) (undo)
m
 
Line 1: Line 1:
Although related, the term encapsulation is often erroneously considered to be interchangeable with information hiding. The ''information'' encapsulated within a class need not be ''hidden'' from the outside (consider public class members).
Although related, the term encapsulation is often erroneously considered to be interchangeable with information hiding. The ''information'' encapsulated within a class need not be ''hidden'' from the outside (consider public class members).
-
In most aspect-oriented programming language implementations, no join points are hidden from aspects. There is an ongoing debate as to whether or not some join points should be hidden from some aspects. Anyone know of good links?
+
In most aspect-oriented programming language implementations, no join points are hidden from aspects. There is an ongoing debate as to whether or not some join points should be hidden from some aspects. ''Anyone know of good links?''

Current revision

Although related, the term encapsulation is often erroneously considered to be interchangeable with information hiding. The information encapsulated within a class need not be hidden from the outside (consider public class members).

In most aspect-oriented programming language implementations, no join points are hidden from aspects. There is an ongoing debate as to whether or not some join points should be hidden from some aspects. Anyone know of good links?


Wiki

Instant Feedback

Edited by the AOSD Steering Committee.  Maintained by the webmaster