Path: csiph.com!x330-a1.tempe.blueboxinc.net!usenet.pasdenom.info!weretis.net!feeder4.news.weretis.net!usenet.ukfsn.org!not-for-mail From: Martin Gregorie Newsgroups: comp.lang.java.programmer Subject: Re: Best Way to Pass Info Between Objects? Date: Tue, 10 Jan 2012 02:11:25 +0000 (UTC) Organization: UK Free Software Network Lines: 22 Message-ID: References: <4dWdnRF6pOQcUJTSnZ2dnUVZ_vidnZ2d@earthlink.com> <54qdnTd-nYZBj5fSnZ2dnUVZ_q2dnZ2d@earthlink.com> <%ozOq.43065$aW6.17493@newsfe09.iad> NNTP-Posting-Host: 84.45.235.129 Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Trace: localhost.localdomain 1326161485 13395 84.45.235.129 (10 Jan 2012 02:11:25 GMT) X-Complaints-To: usenet@localhost.localdomain NNTP-Posting-Date: Tue, 10 Jan 2012 02:11:25 +0000 (UTC) User-Agent: Pan/0.135 (Tomorrow I'll Wake Up and Scald Myself with Tea; GIT 30dc37b master) Xref: x330-a1.tempe.blueboxinc.net comp.lang.java.programmer:11153 On Mon, 09 Jan 2012 12:36:11 +0000, Stefan Ram wrote: > TDD is not the only methodology, where one writes the calls before one > write the callee. In the 70s we already had something called »top-down > programming« where one writes the upper-level methods first and then > implements the operations they call. > Indeed. IIRC I first found the idea of Top-down Incremental Development (TID) in "Software tools in Pascal" and have used it ever since. I like the idea of getting the bugs out of the top level before adding the next level down. I find that my preferred method of writing Java is to do the proper OOD thing for the collection of classes that implement code that's specific to the algorithm to be implemented but often revert to TID when I'm building the framework that will drive the application. -- martin@ | Martin Gregorie gregorie. | Essex, UK org |