Path: csiph.com!x330-a1.tempe.blueboxinc.net!newsfeed.hal-mli.net!feeder1.hal-mli.net!nx01.iad01.newshosting.com!newshosting.com!news-out.readnews.com!transit3.readnews.com!panix!not-for-mail From: Grant Edwards Newsgroups: comp.lang.python Subject: Re: vertical ordering of functions Date: Wed, 4 May 2011 01:09:39 +0000 (UTC) Organization: PANIX Public Access Internet and UNIX, NYC Lines: 16 Message-ID: References: NNTP-Posting-Host: 67-220-17-92.usiwireless.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Trace: reader1.panix.com 1304471379 12237 67.220.17.92 (4 May 2011 01:09:39 GMT) X-Complaints-To: abuse@panix.com NNTP-Posting-Date: Wed, 4 May 2011 01:09:39 +0000 (UTC) User-Agent: slrn/0.9.9p1 (Linux) Xref: x330-a1.tempe.blueboxinc.net comp.lang.python:4594 On 2011-05-03, Jabba Laci wrote: > I'm just reading Robert M. Martin's book entitled "Clean Code". In Ch. > 5 he says that a function that is called should be below a function > that does the calling. This creates a nice flow down from top to > bottom. I generally expect the opposite: callees above, callers below, main at the bottom. However, that's mostly just a habit left over from C programming where such an ordering avoids having to litter the file with forward declarations for functions. -- Grant