> Well I've commented out that line and still have 103 errors, some just
> need a change of syntax, but the very first one is 'Expecting a
> Declaration' followed by Expecting a '{'
>

I assume you know that you want to work on the first error, since it often
causes the rest.


> At the moment I'm wondering if the problem is that CCS doesn't allow
> ASM macro statements which is where the first (of many) Expecting a
> '{' is highlighted.
>

CCS uses #ASM and #ENDASM for its syntax.  You can get the compiler manual
on line.
Er, you said "ASM macro".  That's something I haven't tried. It looks like
the C preprocessor is intended to handle that.


> I've double checked my opening and closing brackets in EditPadPro, and
> they're all there and this code is compiling correctly with my current
> compiler.
>

I always end up paring the problem down to just the few statements causing
the problem.  Usually I find my error before I'm done.

Often an included .h file will cause an error not caught after a return to
the file that included it.


>
> Does CCS have a problem with header files that have
>
> #ifndef _glcKS0108_H
> #define _glcKS0108_H
> "
> "
> #endif
>

I just tried that bit above and it seems to work just fine.  I tend to stick
with simple code and don't try to push their C to the limits; nevertheless I
have ended up using most of the features.  I can't think of anything that
"didn't work", other than a few things that they state explicitly their
compiler doesn't do.  Things like, "arrays of 1-bit variables", and pointers
to various things.

Well, there was a thing or two that didn't work right, but they turned out
to be bugs, most of which had already been fixed by the time I found them.
-- 
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist