Talk:Yo-yo problem

	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.

Original[edit]

This was removed from the original article.

On the other hand, object-oriented programming methodology is structured around data and data types. If the programmer uses this structure to follow and understand the object-oriented program, the problem disappears, as there will be no need to follow the control-flow structure, except during debugging.

I am not sure about this. This sounds a bit ranting. Does anyone care to clarify this? -- Taku 23:01, Jun 5, 2005 (UTC)

With object-oriented design, control flow is not very important for being able to understand the design, because object-oriented design principles enforce that methods can be independently invoked in any order without changing the meaning of each invocation, which means that all important aspects of the program (that is, class invariants) are preserved even if the methods are invoked in different order. This is also the reason why many object-oriented systems use callbacks, where order cannot be enforced due to lack of information for the caller as to correct order. [Any system that uses callbacks in a way that requires that those callbacks are invoked in certain order is flawed, IMO]. The independence from ordering is ensured by the API design principle that says that methods in each interface should be orthogonal to each other. This is sometimes called the "Operand principle" [see Meyer: Object-oriented software construction ], and it states that a method must not have optional parameters, only mandatory parameters. Sometimes the same thing is also called "Shopping list principle". This principle is implied by the open-closed principle (class should be open for extension but closed from modification), because a class is extensible exactly when all parameters to every method are mandatory. For object-oriented design, more important consideration to order of execution is how stack is used (layering), and how different classes (not objects!) relate to each other. esap 16:53, Jun 6, 2005 (UTC)

Lack of Sources Listed[edit]

I noticed there are no sources listed on this wiki page. Robert binder provides an excellent overview of the yo-yo problem in his book, Testing Object-Oriented Systems, Models, Patterns, and Tools. I'm certain he also references some good articles on this subject. I'll spend a bit of time soon adding references to this problem soon. Blutrot (talk) 19:36, 22 May 2009 (UTC)[reply]

[sic][edit]

"Often we get the feeling of riding a yoyo when we try to understand one these [sic] message trees." I don't see what's actually wrong with this sentence, anyone mind explaining? 85.24.223.146 (talk) 13:19, 17 June 2013 (UTC)[reply]