Handling non-standard or unsupported keywords: Difference between revisions
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
Many target compilers for specific systems support specialized non-standard keywords. Although the STRIDE compiler | Many target compilers for specific systems support specialized non-standard keywords. Although the STRIDE compiler supports many of these, from time to time you may run into one that is not supported. This article describes how to handle this. | ||
If an unrecognized keyword in your source file is preventing compilation in STRIDE, you can work around the issue by creating an explicit empty definition (ie macro) for the keyword within STRIDE Studio. | If an unrecognized keyword in your source file is preventing compilation in STRIDE, you can work around the issue by creating an explicit empty definition (ie macro) for the keyword within STRIDE Studio. | ||
Revision as of 22:06, 3 October 2008
Many target compilers for specific systems support specialized non-standard keywords. Although the STRIDE compiler supports many of these, from time to time you may run into one that is not supported. This article describes how to handle this.
If an unrecognized keyword in your source file is preventing compilation in STRIDE, you can work around the issue by creating an explicit empty definition (ie macro) for the keyword within STRIDE Studio.
To create a new definition, from the Studio menu, choose Workspace/Settings, then choose the Compiler tab and add a preprocessor definition for the unrecognized keyword.
For example if your source contains a keyword __inline__ that is not supported by STRIDE and is preventing successful compilation, then you remedy this by adding '__inline__=' to the workspace preprocessor definitions. This line instructs the STRIDE preprocessor to replace occurrence of the keyword with nothing, causing the STRIDE compiler to effectively ignore it.