🚀 go-pugleaf

In article <4h779j$5ep@solutions.solon.com>,
Network News  <news@dcs.warwick.ac.uk> wrote:
>David Thomas Richard Given <dtrg@st-andrews.ac.uk> wrote:
>>Definately. I use lots of white space:
>
><pet peeve>
>Defin*i*tely.
></pet peeve>

That one always gets me... :)

(snip)
>(Sorry about the excessive quoting.  I think it's necessary in this
>case.)
>
>For a contrived example, I find it rather fails to make your point.  I
>find the second version of the function far more understandable.  The
>code is all visually close together, which helps a lot with larger
>sections of code.  Blank lines waste vertical space.  Looking at the
>code, it is immediately obvious that it allocates memory, with error
>checking, then does_something_with the memory, and then frees the
>memory.  Comments and blank lines do not help, and in your first
>version of the code distract one's attention from what really matters
>-- the code.

Well, YM really does V. I don't like the second one because all you see 
is a solid block of code. There aren't any visual cues as to the semantic 
grouping.

It's all really a matter of personal preference. I'm more productive 
using the code I find most readable. You're more productive with the code 
*you* find most readable, even if I don't.

>BTW, there's a bug in the second version.
>
>	if (!variable2 = (char *)malloc(size))

Well, I never use that construct, so I have an excuse...

-- 
-------------------------------------------------------------------------------
   Why do people surf the Information Superhighway? Won't they get run over?
               http://www-hons-cs.cs.st-andrews.ac.uk/~dg
              Sun-Earther David Daton Given  of Lochcarron