> >         Hmm, never mind, I think I've figured things out, seems
> they want you to
> > set things like that up statically, kinda strange but whatever... Sorry
>
> Not really that strange, not knowing the C18 implementation but most C
> compilers put local variables and parameters on the stack
> implementation. Where static variables (even those declared in the local
> context) will go on heap memory. A static local variable is really a
> global that is only in scope within the function.
>
> Just a spot of background for you.

        Actually no, the issue is that the solution I found requires you to place
the variable in specified address of available memory, that is the strange
part. I understand WHY it's done like that (the compiler doesn't know what
hardware resources are available, those definitions are in the linker
script), however I don't like telling a compiler where to put things, it's
counterintuitive and can be dangerous. TTYL

----------------------------------
Herbert's PIC Stuff:
http://repatch.dyndns.org:8383/pic_stuff/

--
http://www.piclist.com hint: The list server can filter out subtopics
(like ads or off topics) for you. See http://www.piclist.com/#topics