[prog] C and curly braces - question of style?

[Jenn Vesperman]

On Wed, 2004-08-25 at 05:42, Jimen Ching wrote:
> On Tue, 24 Aug 2004, Jenn Vesperman wrote:
> >Make life a little easier for my eyes. If I have a really good screen,
> >like my trusty LCD, I can usually see just fine. If I'm working for a
> >company that buys cheap flickery CRTs, they end up spending money on
> >printouts.
> 
> I'm not sure if it is necessary to torture your eyes like this, especially
> when 17" flat screen CRT's are less than $200.

It isn't. But it can be difficult to convince the people with the cash,
sometimes.

> Flickering CRT's aside, I'm not sure how one performs code review with
> hardcopies. 
>
> How does one verify deadlock?  Memory leaks?  Initialization issues?  Etc,
> etc...To validate these problems, you need to look at multiple functions
> in multiple files.  I would imagine hardcopies would make it more
> difficult to do such reviews.  Or are these not the type of reviews being
> done?

More a case of sitting down with the hardcopy code at the desk, pulling
out the keyboard occasionally and inserting debug statements,
compile/test/see-result, turn back to the hardcopy to check where else
the bug might be, since it wasn't there....

You do a lot of reading you're not aware of during most forms of code
reviewing, and if you have a crappy cheap monitor and bad eyes you get
unnecessary headaches.



Jenn V.
-- 
    "Do you ever wonder if there's a whole section of geek culture 
        	you miss out on by being a geek?" - Dancer.
   My book 'Essential CVS': published by O'Reilly in June 2003.
jenn at anthill.echidna.id.au     http://anthill.echidna.id.au/~jenn/