tiens, voila quelqu'un qui assimile le terme encapsulation de la meme maniere que moi et pas dans le sens C++ !
http://www.tonymarston.net/php-mysql/good-bad-oop.html(...)
# 'Encapsulation' means that the class must define all the properties and methods which are common to all objects of that class. All those properties and methods must exist inside a single container or 'capsule', and must not be distributed across multiple locations.
Reference: encapsulation The localization of knowledge within a module. Because objects encapsulate data and implementation, the user of an object can view the object as a black box that provides services. Instance variables and methods can be added, deleted, or changed, but as long as the services provided by the object remain the same, code that uses the object can continue to use it without being rewritten.
juste dessous, il fait bien le distingo : encapsulation - protection de l'implémentation ...
[^] # Re: Marrant, ça...
Posté par Marc Quinton . En réponse au journal Apache/PHP et J2EE. Évalué à 1.
http://www.tonymarston.net/php-mysql/good-bad-oop.html(...)
# 'Encapsulation' means that the class must define all the properties and methods which are common to all objects of that class. All those properties and methods must exist inside a single container or 'capsule', and must not be distributed across multiple locations.
Reference: encapsulation The localization of knowledge within a module. Because objects encapsulate data and implementation, the user of an object can view the object as a black box that provides services. Instance variables and methods can be added, deleted, or changed, but as long as the services provided by the object remain the same, code that uses the object can continue to use it without being rewritten.
juste dessous, il fait bien le distingo : encapsulation - protection de l'implémentation ...