>I still haven't had any luck figuring out what was causing my problem.
>
> I have uploaded my code (an older version that had this problem) to
> http://www.jasonhsu.com/swrwatt_2010_0224_2131.c .  The code as is
> will compile.  Uncommenting the delay_1_msec declaration will cause
> the error to show up.
>
> I agree that I need to figure out why I was getting these cryptic
> function declaration errors even though the same offending lines
> (verbatim) had no such effect in another program.  As a student and as
> an engineer, I have found all too often that political pressure has
> encouraged me to just get the job done rather than take the time to
> understand just what I'm doing.  Since I don't have a professor or
> boss breathing down my neck over this matter, I cannot use this as an
> excuse to pass up this learning opportunity.

Jason,

IIRC you are including some compiler-specific file in the version of the 
program that doesn't work. Is it possible that somewhere in those includes 
there is a

    #define delay_1_msec

This could certainly cause much trouble.

One way to check for this, or similar macro hosings is to get your compiler 
to output a preprocessed source and take a look at it.

-- Bob Ammerman
RAm Systems

-- 
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist