At 08:25 AM 20/12/2002 -0600, you wrote:
>You might also want to go through and take a good look at where you may be
>able to optimize your code a little yourself.  For instance, I found that
>if you use printf() anywhere in the program, it may be better to use that
>than putc().  I have also found other minor things that can save a few
>instructions here and there, such as rearranging the order of operations
>or simplifying statements.
>
>Shawn's suggestion of using #separate is also a good idea, especially if
>you have one huge function you only call once.  If that's tha case,
>though, you may want to look again and see if that function can be split
>up into smaller functions.  It may well make code maintenance easier too.

I think Shawn's suggestion will be a good solution.  There's really not
much I can do to trim code, considering that what I'm implementing is a USB
function, and it was unhappy with the USB interrupt,(actually, it's CCP1
being used as an external interrupt, but anyway)  I think that I can use
separate safely, since when I commented something out, I got worst case
stack use of  4.  With that low a stack use, it's pretty safe to separate a
function or 3.

Thanks for the recommendations
--Brendan

--
http://www.piclist.com hint: The PICList is archived three different
ways.  See http://www.piclist.com/#archives for details.