Talk:Sequential coupling

	This article is within the scope of WikiProject Computing, a collaborative effort to improve the coverage of computers, computing, and information technology on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.ComputingWikipedia:WikiProject ComputingTemplate:WikiProject ComputingComputing articles
Low	This article has been rated as Low-importance on the project's importance scale.
	This article is supported by WikiProject Software.

Bad example of car[edit]

When you step on the gas in a car before you turn the key, you can flood the engine which is also not good. In fact, I can't see where there would be a software class that if you call the "wrong" method, it doesn't fail. It should fail gracefully, but it should definitely not do nothing at all.Fine Arts 18:09, 30 August 2006 (UTC)[reply]

I agree. You should certainly alert the programmer.

Better example?[edit]

A possible better example is a utility library that requires that one call some sequence of "init" functions in order to initialize it and create a useful working environment, rather than encapsulating this behavior in the creation of an object. The curses (programming library) library, for instance. One useful thing to do is to encapsulate the use of that library into a class. --FOo (talk) 11:40, 7 December 2007 (UTC)[reply]

Temporal coupling[edit]

I faced only Temporal coupling term in such meaning. Sequential coupling looks less familiar. 91.103.66.203 (talk) 15:35, 12 January 2018 (UTC)[reply]