c99/c++ localised variable definition

[John-Mark Gurney]

Paul Richards wrote this message on Tue, Feb 01, 2005 at 23:46 +0000:
> On Tue, Feb 01, 2005 at 03:04:37PM -0800, John-Mark Gurney wrote:
> > Paul Richards wrote this message on Tue, Feb 01, 2005 at 19:04 +0000:
> > > On Tue, Feb 01, 2005 at 10:06:24AM -0800, John-Mark Gurney wrote:
> > > > Paul Richards wrote this message on Mon, Jan 31, 2005 at 10:26 +0000:
> > > > 
> > > > [...]
> > > > 
> > > > > I think the loop usage though is one clear example where it is
> > > > > clearer. I think there are others as well; where the usage of the
> > > > > variable is clearly localised it is much easier to see a local
> > > > > definition than to have to jump back and forth to find out what
> > > > > variables are.
> > > > 
> > > > I personally think it isn't.  One thing that I do in python all to
> > > > regularly (because it lacks variable declarations), is attempt to do:
> > > > 	for i in foo:
> > > > 		for j in bar:
> > > > 			for i in baz:
> > > 
> > > That would work fine with c99.
> > 
> > Depends upon your definition of working fine.. :)  it doesn't work fine
> > if you do:
> > 	for i in foo:
> > 		for j in bar:
> > 			for i in baz:
> > 				pass
> > 		print i
> > 
> > When the print i is suppose to return the element from foo, not baz,
> > because you later added baz because of fixing another bug..
> 
> That's true. What's starting to strike me as odd about this thread is
> that all the counter examples are about doing really dumb things. If
> you're a second rate coder who has a tendency to do dumb things then
> there's really no helping you no matter what the style is.
> 
> Surely the issue should be, if you're a good coder and you adhere
> to the adopted style, which style is more likely to result in
> maintainable code.

The issue should be how to make sure all contributions to the FreeBSD
project are maintainable and of good quality not to be buggy...
That is part of why we have the style(9) guide in the first place..
Considering not everyone is a first rate coder, having loose style
guide lines is an accident waiting to happen...

-- 
  John-Mark Gurney				Voice: +1 415 225 5579

     "All that I will do, has been done, All that I have, has not."