On 30 Oct, 05:32, Neil <NeilKu...@worldnet.att.net> wrote:
> Mark L Pappin wrote:
> > Neil <NeilKu...@worldnet.att.net> writes:
>
> >> Mark L Pappin wrote:
> >>> Andrew Jackson <a...@nospam.com> writes:
> >>>>> hi..can anyone tell me why cant i compile this code at PICC
> >>>>> Compiler?
> >>> The presence of '#use' lines says that it's not source intended for a
> >>> C compiler (which PICC mostly is) but for a compiler for some language
> >>> sort-of-a-bit-like C.
> > ...
> >>>>> the compiler stated that <16f84.h> "File cant be opend"
>
> >> Microchip's compiler also is called PICC.
>
> > Their compiler for PIC16 chips isn't, because they don't have one.
> > Their compilers for other chips all appear to be called "MPLAB C
> > Compiler for X".
>
> > mlp
>
> They used to have one.

We tried to use where I once worked. It was unusable because of the
number of bugs.

Leon

Mark L Pappin wrote:
> Neil <NeilKurzm@worldnet.att.net> writes:
> 
>> Mark L Pappin wrote:
>>> Andrew Jackson <alj@nospam.com> writes:
>>>>> hi..can anyone tell me why cant i compile this code at PICC
>>>>> Compiler?
>>> The presence of '#use' lines says that it's not source intended for a
>>> C compiler (which PICC mostly is) but for a compiler for some language
>>> sort-of-a-bit-like C.
> ...
>>>>> the compiler stated that <16f84.h> "File cant be opend"
> 
>> Microchip's compiler also is called PICC.
> 
> Their compiler for PIC16 chips isn't, because they don't have one.
> Their compilers for other chips all appear to be called "MPLAB C
> Compiler for X".
> 
> mlp
They used to have one.

Neil <NeilKurzm@worldnet.att.net> writes:

> Mark L Pappin wrote:
>> Andrew Jackson <alj@nospam.com> writes:
>>>> hi..can anyone tell me why cant i compile this code at PICC
>>>> Compiler?
>> The presence of '#use' lines says that it's not source intended for a
>> C compiler (which PICC mostly is) but for a compiler for some language
>> sort-of-a-bit-like C.
...
>>>> the compiler stated that <16f84.h> "File cant be opend"

> Microchip's compiler also is called PICC.

Their compiler for PIC16 chips isn't, because they don't have one.
Their compilers for other chips all appear to be called "MPLAB C
Compiler for X".

mlp

Hagen Patzke wrote:
> http://www.vermontficks.org/combo2d.htm.

Typo alert: combo2d.htm is the _d_escription.

C-Source:
http://www.vermontficks.org/combo2c.htm

Schematics:
http://www.vermontficks.org/combo2s.htm

hk_gg wrote:
> hi..can anyone tell me why cant i compile this code at PICC Compiler? 

Yes. Your source is from http://www.vermontficks.org/combo2d.htm.

On http://www.vermontficks.org/pic.htm, Mr. Jon Fick says:
"CCS supplies the C compilers that are used to compile my source code. 
Unabashed and liberal use is made of the many built-in functions 
provided by these compilers."

=> The source you posted is for a CCS compiler. The PICC does not 
understand the special CCS built-in functions and '#' directives.

If you like other people to help you (for free, in their spare time), 
then it is only proper to save as much of their time by quoting the 
original source of a project.

Mark

>>> hi..can anyone tell me why cant i compile this code at PICC
>>> Compiler?
> 
> The presence of '#use' lines says that it's not source intended for a
> C compiler (which PICC mostly is) but for a compiler for some language
> sort-of-a-bit-like C.  Thankfully, even the name of that compiler's
> vendor is gone from my brain at this point, so to avoid slandering any
> innocent bystanders I won't even guess.

My apologies: I saw PICC and thought of the excellent HiTech product but 
as you correctly point out, this code isn't likely to be for it.

To the OP: you need to give more background for people to help you. 
Which chip (exactly), which compiler.

	Andrew

Mark L Pappin wrote:
> Andrew Jackson <alj@nospam.com> writes:
> 
>>> hi..can anyone tell me why cant i compile this code at PICC
>>> Compiler?
> 
> The presence of '#use' lines says that it's not source intended for a
> C compiler (which PICC mostly is) but for a compiler for some language
> sort-of-a-bit-like C.  Thankfully, even the name of that compiler's
> vendor is gone from my brain at this point, so to avoid slandering any
> innocent bystanders I won't even guess.
> 
>>> the compiler stated that <16f84.h> "File cant be opend"
> 
> I'll bet that it did not use that message unless you (the OP) have
> deliberately introduced several typos into the message-text file.
> 
> A suggestion: copy-and-paste the exact message text in future.
> 
>>> so how can i find this file?
>>> or someone else can guide me do fix this problem?
>> Which processor are you using?  Hi-Tech include files generally have
>> the form "picXXXX.h" where XXXX is the processor number.
> 
> The file names can be a bit deceptive, since many of them are used for
> groups of processors with similar characteristics.
> 
>> However you can normally include "pic.h"
> 
> You _should_ _always_ use '#include <pic.h>' and not any chip-specific
> header, when writing code for PICC.
> 
>> and that will pick up the correct name
>> (if you specify the processor on the command line).
> 
> ... and with that compiler there is no other way to specify the
> processor.
> 
> But the whole question is moot - the OP is attempting to compile a
> chunk of source obtained from someone else (because if he wrote it
> himself for PICC he would not have used '#use'), but has picked the
> wrong tool.
> 
> mlp
He really needs the Compiler name.  But Microchip's compiler also is 
called PICC.

Andrew Jackson <alj@nospam.com> writes:

>> hi..can anyone tell me why cant i compile this code at PICC
>> Compiler?

The presence of '#use' lines says that it's not source intended for a
C compiler (which PICC mostly is) but for a compiler for some language
sort-of-a-bit-like C.  Thankfully, even the name of that compiler's
vendor is gone from my brain at this point, so to avoid slandering any
innocent bystanders I won't even guess.

>> the compiler stated that <16f84.h> "File cant be opend"

I'll bet that it did not use that message unless you (the OP) have
deliberately introduced several typos into the message-text file.

A suggestion: copy-and-paste the exact message text in future.

>> so how can i find this file?
>> or someone else can guide me do fix this problem?
>
> Which processor are you using?  Hi-Tech include files generally have
> the form "picXXXX.h" where XXXX is the processor number.

The file names can be a bit deceptive, since many of them are used for
groups of processors with similar characteristics.

> However you can normally include "pic.h"

You _should_ _always_ use '#include <pic.h>' and not any chip-specific
header, when writing code for PICC.

> and that will pick up the correct name
> (if you specify the processor on the command line).

... and with that compiler there is no other way to specify the
processor.

But the whole question is moot - the OP is attempting to compile a
chunk of source obtained from someone else (because if he wrote it
himself for PICC he would not have used '#use'), but has picked the
wrong tool.

mlp

> hi..can anyone tell me why cant i compile this code at PICC Compiler?
> 
> the compiler stated that <16f84.h> "File cant be opend"
> so how can i find this file?
> or someone else can guide me do fix this problem?


Which processor are you using?  Hi-Tech include files generally have the 
form "picXXXX.h" where XXXX is the processor number.  However you can 
normally include "pic.h" and that will pick up the correct name (if you 
specify the processor on the command line).

	Andrwe

Check your compiler settings, directories all pointing to the correct
place.

Could do a search for "16f84.h" and place it in your project directory
with your source files.