Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #4584 > unrolled thread
| Started by | Chris Angelico <rosuav@gmail.com> |
|---|---|
| First post | 2011-05-04 08:31 +1000 |
| Last post | 2011-05-04 08:31 +1000 |
| Articles | 1 — 1 participant |
Back to article view | Back to comp.lang.python
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: vertical ordering of functions Chris Angelico <rosuav@gmail.com> - 2011-05-04 08:31 +1000
| From | Chris Angelico <rosuav@gmail.com> |
|---|---|
| Date | 2011-05-04 08:31 +1000 |
| Subject | Re: vertical ordering of functions |
| Message-ID | <mailman.1130.1304461882.9059.python-list@python.org> |
On Wed, May 4, 2011 at 8:08 AM, Jabba Laci <jabba.laci@gmail.com> wrote: > Hi, > > 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 prefer to define my terms before I use them. Classes, functions, etc get defined at the top and called down below. It's a stylistic thing, but it ties in with what you would do in a debate or scholarly document; and if you're skimming such a document and you don't understand a term, you know to scan upwards for its definition. It's just a stylistic thing, you can do it whichever way you think best! Chris Angelico
Back to top | Article view | comp.lang.python
csiph-web