Thanks for sharing that, it makes a good point that the smallest, tightest,
fastest code is not always best if future maintainability is critical.

I personally KNOW that I blew out quite a few brain cells trying to
understand how the heck John Payson's binary to BCD converter works.
Irreparable brain damage.

---
James Newton: PICList webmaster/Admin
mailto:jamesnewton@piclist.com  1-619-652-0593 phone
http://www.piclist.com/member/JMN-EFP-786
PIC/PICList FAQ: http://www.piclist.com

 

> -----Original Message-----
> From: piclist-bounces@mit.edu 
> [mailto:piclist-bounces@mit.edu] On Behalf Of Charles Craft
> Sent: 2004 Aug 28, Sat 15:03
> To: piclist@mit.edu
> Subject: [PIC]: Brute force 16bit to BCD
> 
> 11 bytes of RAM and 183 words of program memory!
> 
> Simulator stopwatch shows 1882 instruction cycles or 1.882 
> msec with the 4 Mhz internal RC oscillator I'm using on the 12F675.
> 
> I looked briefly at the two routines in the PIClist software 
> archive and promptly got brainache. The project I'm working 
> on is fat on time and resources so I created the not so 
> efficent or small, but I hope readable, code below.
> 
<SNIP>


_______________________________________________
http://www.piclist.com
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist