2.   Dummy-Header File & Language Extensions

<< Previous Table of Contents   |   Detailed Index Next >>
1. If your code contains non-ANSI C keywords:

Use the dummy-header-file or the Language extensions to handle non-ANSI C keywords:

Language extensions can be supported by means of either the dummy-header file or the language extensions card of the Options menu:

Let us start with an example:

__usert TBool find_ele( int *arr_p, int amax )

a)   Since ANSI C does not recognize __usert and TBool, you can add a declaration or #define for __usert and TBool in the Project Dummy Header file. Crystal REVS automatically #includes the Project Dummy Header file at the beginning of each file in the project.

You can open the Project Dummy Header file from the "Project" pull-down menu or the "Prj Files" pane of the Browse Window.

The Project Dummy Header file is like any other header file, you can edit it and save it. You can #include other files in it.

        #ifndef dummy_header_is_included_once
        #define dummy_header_is_included_once 1
        # define __usert
        typedef int TBool;

After you modify the dummy-header file, save it and Reparse All files.

b)   Or you can use the Language Extensions card of the Options Menu. You can add a new scheme. Enter TBool in the "Types" and click . Similarly add __usert to the "Others" column.

(Adding to the "Others" column has the same effect as #define __usert as shown above.)

Both Project Dummy Header file and Options settings are saved on a per-project-basis.

<< Previous Table of Contents   |   Detailed Index Next >>