PCDIDE COMPILER Custom Computer Services Inc (CCS), PCDIDE COMPILER Datasheet - Page 42

PCD C-COMPILER PIC24, DSPIC

PCDIDE COMPILER

Manufacturer Part Number
PCDIDE COMPILER
Description
PCD C-COMPILER PIC24, DSPIC
Manufacturer
Custom Computer Services Inc (CCS)
Type
Compilerr
Datasheet

Specifications of PCDIDE COMPILER

For Use With/related Products
Microchip PIC24/dsPIC®
Lead Free Status / RoHS Status
Not applicable / Not applicable
Other names
429-1008
Additional Note: If there is only one source file in the project, it will be compiled and linked in one
step, a *.o file will not be created. A *.o file, that has already been compiled can be added to the
project and linked during the make / build process.
Additional Notes:
To make a variable or function private to a single unit, use the keyword static. By default, variables
declared outside a function at the unit level are visible to all other units in the project. If the static
keyword is used on a function or variable that is accessed outside of the local unit, a link time error
will occur.
If two units have a function or a unit level variable of the same name, an error will occur unless one
of the following conditions is true:
For a project with multiple compilation units, it is best to include a file such as project.h which
includes the #includes, #defines, pre-processor directives, and any other compiler settings that are
the same for all the units in a project.
28
· The identifier is qualified with the keyword static.
· The argument list is different for both functions, allowing them to co-exist according to
normal overload rules.
· The contents of the functions are identical, such as when the same *.h file is included in
multiple files, then the linker will delete the duplicate functions.

Related parts for PCDIDE COMPILER