I like this analogy: writing assembler is like writing poetry. Every word, nay every syllables , must be polished and in perfect harmony with its neighbours. And the result makes your soul soar Writing in a high level language like Algol or Fortran or Pascal or VBasic is like writing a monthly progress report. Simple, easy to read but giving you no real pleasure in the achievement. And writing in C, which can't be graced as high level, is like using pidgin English. You occasionally get a euphonic burst but it is more often ugly and difficult to interpret. On 25 Aug 2016 11:36 p.m., "Denny Esterline" wrote: > > > > > > True, if that's all you ever want to do with that system. I still thin= k > > it's a bad habit though. > > > > I don't know. I've had some time to think about it, I think the bad hab= it > may actually be on the other side of that. I think it's another variation > of "I do it this way because this the way I've always done it". > I think the bad habit was mine, Not informing myself of all the options a= nd > making a judgment based on data. > > I believe it was Donald Knuth that said "Premature optimization is the ro= ot > of all evil." Probably a bit of hyperbole, but definitely applicable to > this project. I'm sure the math could be optimized to allow the processor > to spend 99.997% of it's time waiting instead of 99% Not a meaningful > difference. I think back to all the projects I've done that I did spend t= he > time to optimize the math, I wonder how many of them really needed it. > -- > http://www.piclist.com/techref/piclist PIC/SX FAQ & list archive > View/change your membership options at > http://mailman.mit.edu/mailman/listinfo/piclist > --=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 .