From: benjohn@...
Date: 2006-05-10T00:12:22+09:00
Subject: Re: Method Size - Best Practices

Ara:
*snip*
> i think this is a bit silly really,  i have several image processing
> programs
> that are 5000 lines of code.
*snip*

Having written a lot of image processing and graphics code, I used to
also feel that way. I've generally found though, that it is possible to
break down these functions (once you find a reusable pattern in them),
and doing so does render them more understandable.

Sometimes they don't come out being as quick, and very ocasionally, a
nice way to write something can make it hard to optimise (often, I've
found that it makes it easier). In cases like this though, I start
wanting to describe my algorithm at a higher level, and have the actual
code be generated by some other mechanism.

Having said the above, I have had IP problems where I've not been able
to find a nice way to break them down, and have moved on as it's not
been that important, so I don't claim it is universally true :)