On Sun, 2014-04-13 at 12:52 -0400, Larry Bradley wrote:

> I hope I'm not preaching to the choir, but I spent far too many hours
in
> my career trying to figure out what on earth THAT piece of code is
> doing. And many times it was MY code.

I resemble that!

Perhaps I'm a bit prejudiced, but I tend to feel like folks who fixate
on performance first just haven't had enough experience.  It seems like
you ALWAYS have to go back to old code, even when it was throw-away, or
you thought it was.

Just last week I re-used a chunk of code I wrote in the 80's - the stuff
has an endless life,

I don't think one should be sloppy, tho.  One of the advantage of C over
many languages is that it tends to put your inefficiencies in your face,
so programmers tend to not write really inefficient stuff in the first
place.

Good organization, logical structure, code that makes sense and is
readable, then if you need performance or memory or whatever, then
tweak.  The result will almost always outperform code where the
programmer was so fixated on some convoluted "cool" algorithm that he
lost sight of the forest.  And you will also be less likely to fight
some arcane bug.

--McD


--=20
http://www.piclist.com/techref/piclist PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist
.