I can't disagree, in particular when something doesn't work correctly=20
(or should I say as expected).  :) :) Sometimes one can spend a lot of=20
time. If it's getting the job done correctly, I tend to let a sleeping=20
dog lay. :)

I had the stuff working in a small program I was using for debugging.=20
When I moved it to the full code and ran it, I got the stack overflow.=20
I'll just write my own routines to write to the USArt.

On 8/20/2010 1:36 PM, sergio masci wrote:
>
> compiler warnings should always be taken seriously. The only time you
> should dismiss them is when you are sure you are doing things correctly
> (and even then maybe you should think again).
>
>   =20
--=20
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist
.