Sequential coupling in code
Posted
by dotnetdev
on Stack Overflow
See other posts from Stack Overflow
or by dotnetdev
Published on 2010-04-26T08:51:54Z
Indexed on
2010/04/26
8:53 UTC
Read the original article
Hit count: 162
oop
|anti-patterns
Hi,
Is sequential coupling (http://en.wikipedia.org/wiki/Sequential_coupling) really a bad thing in code?
Although it's an anti-pattern, the only risk I see is calling methods in the wrong order but documentation of an API/class library with this anti-pattern should take care of that. What other problems are there from code which is sequential? Also, this pattern could easily be fixed by using a facade it seems.
Thanks
© Stack Overflow or respective owner