Method chaining: Difference between revisions

Content deleted Content added
Beroal (talk | contribs)
Rationale: Dead link deleted. The claim "the difficulty humans have with deeply nested method calls" is not substantiated by the link.
Monkbot (talk | contribs)
m top: Task 16: replaced (1×) / removed (0×) deprecated |dead-url= and |deadurl= with |url-status=;
Line 8:
|quote = In order to simplify repeated object interactions on the same object the old trick ''Method Chaining'' originating the world of Smalltalk should be enforced. The idea is to let methods return<code> this </code>rather than<code> void</code>, thus affecting especially<code> set() </code>and<code> add() </code>methods. Method chaining arose during the designers of Smalltalk pursuit to minimize the number of keywords in the language, which lead to the discovery that<code> void </code>is an unnecessary keyword!.
|url = http://firstclassthoughts.co.uk/java/method_chaining.html
|deadurlurl-status = yesdead
|archiveurl = https://web.archive.org/web/20110222112016/http://firstclassthoughts.co.uk/java/method_chaining.html
|archivedate = 2011-02-22
|df =
}}</ref>