This week's book giveaway is in the General Computing forum. We're giving away four copies of Arduino in Action and have Martin Evans, Joshua Noble, and Jordan Hochenbaum on-line! See this thread for details.
Yes, in this case classes will be tightly coupled. This is a bad thing.
Wait sorry, I thought you said variables, not methods. When A calls methods of B, it will big coupled to B, but not nearly as tight as it would be if it accessed a public variable of B. The latter case is very very bad.
So Stephan does that mean only if a class accesses variable of another class then it is tightly coupled to another class and it is also bad encapsulation. AM i right ??......
And in K.S book it had written that " Tight Coupling is the undesirable state of having classes that has many references to each other ,not well encapsulated..i understood this much but this last statement which says
and the breadth of API usage is more ....So what does this statement means ??