I am not a programmer but I play one at work, when I am not playing an
EE, machinist, or janitor.  I am puzzled by the following question &
answer:

> >2) If I have to write functions for CCS, are these functions
> not already
> >included
> >in the higher price tag of Hi-Tech 'C'?
>
> Some, probably not all. HiTech provides a number of example libraries,
> which I usually modify to suit my needs. But I _can_ modify
> them (because I
> have the full source code) -- there's no way to modify the
> code generated
> by the built-in functions of CCS, there's not even a simple
> way to use them
> as a base for writing your own (other than copying from the generated
> assembler listing). And if you want to inspect them, you have
> to look at
> the generated assembler code, not at the source C code. One
> of the reasons
> why I prefer libraries over built-in functions (and one of
> the reasons why
> standard C was designed that way).
>
Which CCS functions are not available as C source?  The STDIO, X10, LCD,
and Dallas touch functions are all plain text C source files.  Something
like Setup_counters() is just some defines and stuffing the results into
registers.  You are never going to write PIC C code without the uP
datasheet at hand anyway so I don't need the compiler to tell me which
registers the counters use.  I don't understand the problem.

I would also add that I have never run into a bug in CCS that I couldn't
code around, like changing a case statement to a string of if-thens or
simillar.  Usually when I do code around what I thought was a bug I find
it was really pilot error after all.  A bug would have to be pretty
catastrophic for me to sit on my hands and wait for the compiler authors
to fix it.  My customers aren't that patient!

Sherpa Doug

--
http://www.piclist.com#nomail Going offline? Don't AutoReply us!
email listserv@mitvma.mit.edu with SET PICList DIGEST in the body