Encapsulation principle

Question

There is some kind of object-oriented engineering principle that formulates something like "a class, should only know about the class contracts that it takes as arguments, or any internal ones that it uses."

Counter example in C ++:

Foo::bar( Baz* baz)
{
  baz()->blargh()->pants()->soil();  // this is bad, Foo knows about blarghs and pants
}

Does this principle have a name? In addition, it would be nice to see the actual principle, not my paraphrase above.

Answer 1

law demeter _{thanks Jim Burger} He speaks:

(LoD) - , - . - 1987 " ". , - ( ).

Answer 2

(- baz), , . (, , ). : S.O.L.I.D.

, , , . .

Answer 3

SOLID. , . , SRP.

- - . . , OO.

Answer 4

I would say here that good encapsulation helps reduce coupling - this is a good goal for any decent encapsulation, except obviously.