I use the CC5X compiler for my projects, and have two pieces of code on line
about them (with copious comments, even.  Oooh!).  they are built for the f8xx
rather than the f84, but should be understandable.  I implement the strings in a
different way using a seperate function.  In the end this is how the c-compiler
implements in the assembly, and it's the pic mindset that I had when creating
them.  Anyway, you can see them here:

LCD code (16c66):
http://ubasics.com/adam/electronics/lcd/cc5xlcd.c

LCD, RS-232 (hardware UART), A/D, and keypad(16F876):
http://ubasics.com/adam/electronics/ha/code.shtml#code

In the second example my tabs were 3 spaces, so the coding and commenting will
probably look improperly indented if you have yours set to higher than 3 spaces.

-Adam

Tobie Horswill wrote:
>
> Blars,
>
>     This is precisely why I am addressing these questions to the list, to
> learn. I certainly never meant, and am very sorry one might think I implied,
> that the CC5X compiler was bugged. This is the first PIC C compiler I try
> and I'm very grateful it's maker has made it freely available for testing. I
> find it to be a great tool. Thank you very much for clarifying the use of C
> strings for me. I will be very careful writing my next posts so they don't
> seem to imply anyone else's incompetence than mine.
>
> Kind regards,
>
> Tobie
>
> >
> > Before you start declaring bugs in a compiler, you should at least
> > try to learn the language first.
> >
> > --
> > Blars Blarson                                   blarson@blars.org
> >                                 http://www.blars.org/blars.html
> > "Text is a way we cheat time." -- Patrick Nielsen Hayden
>
> --
> http://www.piclist.com hint: To leave the PICList
> mailto:piclist-unsubscribe-request@mitvma.mit.edu

--
http://www.piclist.com hint: To leave the PICList
mailto:piclist-unsubscribe-request@mitvma.mit.edu