Encapsulation, the principle of (from the user), is the process of hiding the data structures of the 350-018 class and allowing changes in the data through a public interface where the incoming values are checked for validity, and so not only it permits the hiding of data in an object but also of behavior. This prevents clients of an interface from depending on those parts of the implementation that are likely to change in future, thereby allowing those changes to be made more easily, that is, without changes to clients. In modern programming languages, the principle of information hiding manifests itself in a number of ways, 640-801 including encapsulation and polymorphism.
This concept describes a relationship between two (or more) types, or classes, of objects in which one is said to be a "subtype" or "child" of the other, as result the "child" object is said to inherit features of the parent, allowing for shared functionality, this lets programmers re-use or reduce code and simplifies the development and maintenance of software.
Inheritance is also commonly held to include subtyping, whereby one type of object is defined to be a 640-816 more specialized version of another type (see Liskov substitution principle), though non subtyping inheritance is also possible.
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment