vertical ordering of functions

[MRAB]

On 03/05/2011 23:31, Chris Angelico wrote:
> On Wed, May 4, 2011 at 8:08 AM, Jabba Laci<jabba.laci at 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!
>
You also need to remember that in Python, function and class
definitions are _not_ declarations, but statements which have the
effect of adding a name to the namespace.

If you try to call a function before the flow of control has seen the
function definition, you'll get a NameError.