Yes, I meant expensive. :)



I do try to use memory specific pointers where I can. I'm not really sure why I didn't have a memory specific pointer as a function argument here. Changing that will mean that the function will cost less to call, but it's size shouldn't be affected.

I have noticed that all of the standard library routines use generic pointers to be as general as possible. Would you recommend trying to re-implement some of these routines using memory specific arguments? I only recently started using the library functions where before I hand coded everything thinking that library were always going to be too expensive. Now I'm trying to find a good balance between not reinventing the wheel and squeezing the code size down.

Thanks for your observations!

--David