created by harry h. cheng, 2009 mcgraw-hill, inc. all rights reserved. c for engineers and...

Created by Harry H. Cheng, 2009 McGraw-Hill, Inc. All rights reserved.

C for Engineers and Scientists: An Interpretive Approach

Chapter 7: Preprocessing DirectivesOutline

Introduction Symbolic Constants and Macros Source File Inclusion Conditional Compilation Predefined Macros A Sample Application Problem Pragma Directive NULL Directive Converting Token to Strings Token Merging in Macro Expansions Line Control Error Directive Predefined Macros in Ch



Introduction

• Preprocessing

– Affect program preprocessing and execution

– Capabilities

• Inclusion of additional C source files

• Definition of symbolic constants and macros

• Conditional preprocessing of a program

• Format of preprocessing directivesA preprocessing directive consists of a sequence of preprocessing tokens that

begins with a pound sign #, which must be the first non-space character on the

line. Some preprocessing directives are listed below.



Directive Description

#define Define a preprocessor macro.

#elif Alternatively include some text based on the value of another expression, if the previous #if, #ifdef, #ifndef, or #leif test failed.

#else Alternatively include some text, if the previous #if, #ifdef, #ifndef, or #elif test failed.

#endif Terminate conditional text.

#error Produce a compile-time error with a designated message.

#if Conditionally include text, based on the value of an expression.

#ifdef Conditionally include text, based on whether a macro name is defined.

#ifndef Conditionally include text, based on if a name is not a defined macro.

#include Insert text from another source file.

#line Give a line number for message.

#pragma Compiler/interpreter specific features, not in C standard

# Null directive

defined Preprocessing operator that yields 1 if a name is defined as a preprocessing macro and 0 otherwies; used in #if and #elif.



Symbolic Constants and Macros

• The #define Preprocessing Directive

– This preprocessing directive is used to create symbolic constants and macros.

• Form

#define identifier replacement-list

defines an object-like macro that causes each subsequent instance of the macro names to be replaced by the replacement-list of preprocessing tokens that constitute the remainder of the directive. The new-line is a character that terminates the #define preprocessing directive.



• Symbolic constantsThe simple form of macro is particularly useful for introducing named

constants into a program. It allows for easier modification of the

constants later on.When programs are processed, all occurrences of

symbolic constants indicated by identifier are replaced by the

replacement-list.

Example: #define BLOCK_SIZE 0x100

we can write int size = BLOCK_SIZE;

instead of int size = 0x100;

in the program.

Note: Cannot redefine symbolic constants with different values by multiple

#define statements



• A preprocessing directive of the form

#define identifier(identifier-list-opt) replacement-list new-line

defines a function-like macro with arguments, similar syntactically to a function call. The parameters are specified by the optional list of identifiers.

Example: if a macro mul with two arguments is defined by

#define mul(x,y) ((x)*(y))

then the source program line

result = mul(5, a+b);

is replaced with

result = ((5)*(a+b));



NOTE: Parentheses are important in macro definitions.

Example: If macro mul is defined as

#define mul(x,y) (x*y)

The statement result = mul(5, a+b);

in the source program becomes result = (5*a+b);

The evaluation will be incorrect.



• #undef– Undefine a symbolic constant or macro, which can later be

redefined.

Example:

#define mul(x,y) ((x)*(y))

/* … */

#undef mul

int mul; /* mul can be used after it is undefined */



Source File Inclusion• The #include Preprocessing Directive

– Copy of a specified header file included in place of the directive. It has following two common forms.

1)#include <header.h> – Searches standard library for header file and replaces the directive

by the entire contents of the file. – In Ch, the header is searched according to the paths specified by the

the system variable _ipath. C compilers in Unix will typically search the header file in the directory /usr/include. In Visual C++, the header file is searched based on the paths in the environment variable INCLUDE.

or cl –I C:/home/assount/include program.c

– Used for standard library files• #include “header.h"

– C compilers and interpreters will first search the header file in the same directory where the file is being processed, which typically is the current directory.

– Then search the header file in the paths as if it was included by #include <header.h>.



• Applications

– Loading header files

#include <stdio.h>– Programs with multiple source files to be

compiled together– Includes user defined header files which have

common declarations and definitions (classes, structures, function prototypes, and macros)



Conditional Compilation

• Conditional compilation – Enables the user to control the compilation of the program, screen

out portions of source code that are not to be compiled.

• Structure– The structure is similar to if and else statement in C.

• Conditional preprocessing directives– #if, #else, #elif, and #endif



• Preprocessing directives of the forms

#if expr1

/* ... */

#elif expr2

/* ... */

#else

/* ... */

#endif

check whether the controlling expression evaluates to nonzero. Every #if ends with #endif

Example:

#if defined(_HPUX_)

printf(“I am using HP-UX\n”);

#elif defined(_WIN32_)

printf(“I am using Windows\n);

#endif



• Preprocessing directives of the forms

# ifdef identifier# ifndef identifier

check whether the identifier is or is not currently defined as a macro name.

– #ifdef identifier is the short form of

#if defined(identifier)

– #ifndef identifier is the short form of

#if !defined(identifier)

• Each directive’s condition is checked in order. If it evaluates to false (zero), then the group that it controls is skipped: directives are processed only through the name that determines the directive in order to keep track of the level of nested conditionals.

• Only the first group whose control condition evaluates to true (nonzero) is processed. If none of the conditions evaluates to true, and there is a #else directive, then the group controlled by the #else is processed; if lacking a #else directive, then all the groups until the #endif are skipped.



• Comment out a segment of code– Comment out code segment which contains /* ... */

– Use following format to comment out the segment of code

double d = some_func();

#ifdef JUNK

/* This code segment will be commented out */

printf(“d = %f\n”, d);

#endif

The code segment will be commented out when JUNK is not defined, To uncomment the code segment, define JUNK or remove #ifdef JUNK and #endif.



• Debugging code

#define DEBUG

/* ... */

double x;

x = some_func();

#ifdef DEBUG printf(“The value of x = %f\n”, x); #endif

– Defining DEBUG to print out the value of x.

– After debugging, remove #define statement. The debugging statements are ignored.



• To include a header file in a program only once, it istypically handled using the combination of the followingpreprocessing directives #ifndef, #define, and #endif. For example, a header file header.hmay consist of the following code fragment.

#ifndef HEADER_H #define HEADER_H /* code */ #endif



Sample Problem:

The system in Figure1 (a) consists of a single body with mass m moving on a horizontal surface. An external force p acts on the body. The coefficient of kinetic friction between body and horizontal surface is . The freebody diagram for the system is shown in Figure1 (b).

Figure1: The system diagram and FBD of a sample problem



The nomenclature related to the modeling of the system.is listed below. m -- mass of the body

x -- position of the bodyv -- velocity of the bodya -- acceleration of the bodyg -- gravitational acceleration -- friction coefficient f -- friction force N -- normal force

Equation of motion: The equation of the motion of the system can be derived based on the Newton's second law. N = mg (1) f = N (2)

p-f = ma (3)

From equation (1), (2) and (3), the formula for calculating the acceleration of the rigid body can be derived as follows. a = (p- mg)/m (4)



Problem Statement:

For the system shown in Figure1(a), given m = 5 kg, g = 9.81 m/s2,

= 0.2. The external force p is expressed as a function of time t,

p(t) = 4(sin(t)-3)+20 when t >= 0

write a program to calculate the acceleration a when t = 2 seconds .

(1) Solve acceleration using macros for formulas of force p and acceleration a.

(2) Solve acceleration using functions for force p and acceleration. The function prototypes and macros shall be defined in header file accel.h.



Program 1:

/* File: accelmacro.c */#include <stdio.h>

#define M_G 9.81#define FORCE(t) (4*(sin(t)-3)+20)#define ACCEL(p, mu, m) (((p)-(mu)*(m)*M_G)/(m))

int main() { double a, p, mu, m, t;

mu = 0.2; m = 5.0; t = 2.0; p = FORCE(t); a = ACCEL(p, mu, m); // or a = ACCEL(FORCE(t), mu, m); printf("Acceleration a = %f (m/s^2)\n", a); return 0;}

Output: Acceleration = 1.364823 (m/s^2)



/* File: accel.h */#ifndef ACCEL_H#define ACCEL_H

#define M_G 9.81

double force(double t);double accel(double t, double mu, double m);

#endif

/* File: accelhead.c */#include <stdio.h>/* local header file */#include "accel.h"

int main() { /* declare variables */ double a, mu, m, t;

/* Initialize variables */ mu = 0.2; m = 5.0; t = 2.0; /* processing */ a = accel(t, mu, m); /* display the output and termination */ printf("Acceleration a = %f (m/s^2)\n", a); return 0;}

double force(double t) { double p;

p = 4*(sin(t)-3)+20; return p;}

double accel(double t, double mu, double m) { double a, p;

p = force(t); a = (p-mu*m*M_G)/m; return a;}

Program 2:



Predefined Macros• Macros defined in C

Macro Name Description

__LINE__ The line number of the current source program line which is expressed as a decimal integral constant

__FILE__ The name of the current source file which is expressed as a string constant.

__DATE__ The calendar date of the translation which is expressed as a string constant form “Mmm dd yyy”. Mmm is produced by asctime().

__TIME__ The current time which is expressed as a string constant of the form “hh:mm:ss”, as returned by asctime().

__STDC__ The decimal constant 1 for C comforming impelementtation.

__STDC_VERSION__ The decimal constant 199901L for C99 comforming implelemtation



Example:

/* filename: predefined.c */#include <stdio.h>

int main() { printf("__FILE__ = %s\n", __FILE__); printf("__LINE__ = %d\n", __LINE__); printf("__DATE__ = %s\n", __DATE__); printf("__TIME__ = %s\n", __TIME__);#ifdef __STDC__ printf("__STDC__ = %d\n", __STDC__);#endif#ifdef __STDC_VERSION___ printf("__STDC_VERSION__ = %d\n", __STDC_VERSION__);#endif return 0;}



Output:

__FILE__ = predefined.c

__LINE__ = 6

__DATE__ = Feb 24 2003

__TIME__ = 00:09:42

__STDC__ = 1

__STDC_VERSION_ = 199901



/* File: printerror.c */#include <stdio.h>#define printerror() printf("Error in %s:%s():%d\n", \ __FILE__, __func__, __LINE__);

void funcname1() { printerror();}void funcname2() { printerror();}

int main() { funcname1(); funcname2(); return 0;}

Example

Error in printerror.c:funcname1():7Error in printerror.c:funcname2():10

Output



Pragma Directive• A preprocessing directive of the form #pragma pp-tokens-opt new-line

is called a pragma directive. It is compiler/interpreter dependent.

• Some preprocessing token names for the pragma directive in Ch are defined below.

Pragma Name Value of Argument

remvar(arg) Remove the global or top level variable arg

import “filename” Includes the file filename. It searches for the file in the current directory first, then the directories specified by _path.

import <filename> Includes the file filename. It searches for the file in only the directories specified in _path.

importf “filename” Includes the file filename. It searches for the file in the current directory first, then the directories specified by _fpath.

importf <filename> Inlcudes the file filename. It searches for the file in only the directories specified in _fpath.

pack() Automatic alignment of structure fields.

package <pname> Add _ppath/pname/bin to _path, _ppath/pname/lib to _fpath, _ppath/pname/include to _ipath, _ppath/pname/dl to _lpath.

_fpath <path> Add CHHOME/toolkit/lib/path to _fpath.



‡ Slides for optional topics in C



• The following form

#include pp-tokens

is also permitted. The preprocessing tokens after #include in the directive are processed just as normal text.



NULL Directive


#new-line

has no effect on the program.

• The line is ignored.



• The # token appearing within a macro definition is recognized as a unary stringization operator.

• In a replacement list, if a parameter is immediately preceded by a # preprocessing token, both are replaced by a single character string literal preprocessing token that contains the spelling of the preprocessing token sequence for the corresponding argument.

Example:

> #define TEST(a) #a> printf(“%s”, TEST(abcd))abcd

– The macro parameter abcd has been converted to the string constant “abcd”. It is equivalent to

> printf(“%s”, “abcd”)

Converting Token to Strings



• Each occurrence of white space between the argument’s preprocessing tokens becomes a single space character in the character string literal. White space before the first preprocessing token and after the last preprocessing token composing the argument is deleted.

Example:

> #define TEST(a) #a

> printf(“1%s2”, TEST( a b ))

1a b2

– The argument is turned into the string constant “a b”.



Token Merging in Macro Expansions• The merging of tokens to form new tokens in C is controlled by the

presence of the merging operator ## in macro definitions.

• The common use of concatenation is concatenating two names into a longer name. It is possible to concatenate two numbers, or a number and a name, such as ‘1.5’ and ‘e3’, into a number.

Example:

> #define CONC2(a, b) a ## b

> #define CONC3(a, b, c) a ## b ## c

> CONC2(1, 2)

12 // numbers ‘1’ and ‘2’ concatenated to ‘12’

> CONC3(3, +, 4)

7 // ‘3’, ‘+’, and ‘4’ becomes ‘3+4’, which equals ‘7’

> printf(“CONC2(1,2) = %d”, CONC2(1,2))

CONC2(1,2) = 12



Line Control

• The #line directive can be used to alter the line numbers assigned to the source code. This directive gives a new line number to the following line, which is then incremented to derive the line number for subsequent lines.


#line digit-sequence new-line

causes the implementation to behave as if the following sequence of source lines begins with a source line that has a line number as specified by the digit sequence.


#line digit-sequence “s-char-sequence-opt” new-line

sets the presumed line number similarly and changes the presumed name of the source file to be the contents of the character string literal. The name of the source file is stored in the predefined macro __FILE__ internally.



Example:

/* FILENAME: linefile.c */

#include <stdio.h>

int main() {

printf(“before line directive, line number is %d \n”, __LINE__);

printf(“the FILE predefined macro = %s\n”, __FILE__);

#line 200 “newname”

printf(“after line directive, line number is %d \n”, __LINE__);

printf(“The FILE predefined macro = %s\n”, __FILE__);

return 0;

}

Output:

before line directive, line number is 4

the FILE predefined macro = linefile.c

after line directive, line number is 200

the FILE predefined macro = newname



• A preprocessing directive of the form #error pp-tokens-opt new-line

causes the implementation to produce a diagnostic message that includes the specified sequence of preprocessing tokens and the interpretation to cease.

Example:

/* FILENAME: error.c */

#include <stdio.h>

#define MACRO

int main() {

#ifdef MACRO

#error This is an error, if your code reach here

/* the code here will not be processed */

#else

printf("ok \n");

#endif

return 0;

}

Error Directive



Output:

ERROR: #error: This is an error, if your code reach here

ERROR: syntax error before or at line 6 in file ’error.c'

==>: #error This is an error, if your code reach here

BUG: #error This is an error, if your code reach here<== ???

WARNING: cannot execute command ‘error.c’



‡ Slides for optional topics in Ch



• Predefined Macros in Ch


_CH_ The decimal constant 1.

_CHDLL_ The decimal constant 1 if dynamic link libraries are supported. Otherwise, not defined.

_GLBOALDEF_ The decimal constant 1 when defined macros are in program scope. Undefine it when defined macros in a program dot files, and function files are unrelated to each other.

_SCH_ The decimal constant 1, when Ch is invoked as safe shell. Otherwise, not defined.



• Platform-dependent predefined macros in Ch


_DARWIN_ The decimal constant 1, when Mac OS X is used. Otherwise, it is not defined.

_HPUX_ The decimal constant 1, when HP-UX OS is used. Otherwise, it is not defined.

_LINUX_ The decimal constant 1, when Linux OS is used. Otherwise, it is not defined.

_SOLARIS_ The decimal constant 1, when Solaris OS is used. Otherwise, it is not defined.

_WIN32_ The decimal constant 1, when Windows OS is used. Otherwise, it is not defined.

created by harry h. cheng, 2009 mcgraw-hill, inc. all rights reserved. c for engineers and...

Documents

interpretive approach

interpretive approach

interpretive approach

named constants

macro mul

macro names

macro definitions

b slide