variable inirialization and loop forms (was Re: why no "do : until"?)

Simon Brunning SBrunning at trisystems.co.uk
Thu Jan 4 04:25:19 EST 2001


> From:	grey at despair.rpglink.com [SMTP:grey at despair.rpglink.com]
> On Wed, 3 Jan 2001 13:40:38 +0100, Alex Martelli <aleaxit at yahoo.com>
> wrote:
> >Initializing variables *to correct values* is a great thing -- but using
> >*arbitrary* values for the initialization isn't optimal style.
> 
>     I still stand that initting a variable is just that, setting it to a
> known, arbitrary value.
 
I've had just about enough of this. It strikes me that the root of this
particular spat is that people are using two different definitions of the
work 'arbitrary'. /F, Alex and others are using it to mean that one
particular value (the 'arbitrary' value) has a special meaning. Steve is
using it to mean any old value.

Rather than get into an argument as to which of these is the *correct* use
of the word (FWIW, my reading of the OED offers some support for *both*
meanings), let's just stop using the word altogether in this thread, eh?

Having a quick look at Steve McConnell's 'Code Complete (a Bible to me), he
refers to what /F is objecting to as 'a variable with a hidden meaning', or
'hybrid coupling'. Hmm, don't like that second one much. Let's go with the
first.

Cheers,
Simon Brunning
TriSystems Ltd.
sbrunning at trisystems.co.uk
It is not necessary to change. Survival is not mandatory. - Dr. W. Edwards
Deming




-----------------------------------------------------------------------
The information in this email is confidential and may be legally privileged.
It is intended solely for the addressee. Access to this email by anyone else
is unauthorised. If you are not the intended recipient, any disclosure,
copying, distribution, or any action taken or omitted to be taken in
reliance on it, is prohibited and may be unlawful. TriSystems Ltd. cannot
accept liability for statements made which are clearly the senders own.




More information about the Python-list mailing list