The Linux Development Platform Configuring, Using, and ... - Classes

More documents

Recommendations

Info

CH07.fm Page 206 Monday, October 7, 2002 9:12 PM 206 Chapter 7 • Miscellaneous Tools This is sometimes useful if you just want to test the behavior of indent without modifying a file. The most efficient use of indent is through a shell script that goes into each directory of the source code tree and indents each and every file in the project. You may also create a rule in the makefile of a project to indent all files in one or all directories. A typical makefile rule may look like the following: indent: indent *.c indent *.cpp indent *.h In the case of a project with multiple subdirectories, you can have a more sophisticated rule. Taking an example from Chapter 4, where we have four subdirectories, you can use the following rule to go into each directory and indent all C source code files. SUBDIRS = $(COMDIR) $(FTPDIR) $(TFTPDIR) $(DNSDIR) indent: for i in $(SUBDIRS) ; do \ ( cd $$i ; indent *.c) ; \ done Keep in mind that after indenting all of the files, you may have to build the whole project because source code files have been modified. In big projects this process may take a while. Indent uses a configuration file called .indent.pro, which should be present in the current directory or in your home directory. You can use this file to set options that you always use. If the file is present in the current directory, it is used instead of the file in the home directory of the user. By creating a different .indent.pro file in different directories of a project, you can apply different indentation rules in different directories. This is especially useful when a project uses multiple languages. For example, indentation rules may be different for C, C++ and assembly language files. 7.1.2 Selecting Coding Styles Different coding styles are in use by programmers. Some common styles are defined in indent program and these may be invoked by a single option at the command line. The most common style of coding in the open source is the GNU style. This style can be applied using –gnu option at the command line. Options, which are used with the GNU style, are listed below: -nbad -bap -nbc -bbo -bl -bli2
CH07.fm Page 207 Monday, October 7, 2002 9:12 PM Using indent Utility 207 -bls -ncdb -nce -cp1 -cs -di2 -ndj -nfc1 -nfca -hnl -i2 -ip5 -lp -pcs -nprs -psl -saf -sai -saw -nsc -nsob A list of all the options and their meanings are presented later in this chapter. You can override a particular option in a style by explicitly typing it on the command line. The other commonly used style is Kernighan and Ritchie style, also known as K&R style. This style is applied using the –kr option at the command line and it sets the following options. -nbad -bap -bbo -nbc -br -brs -c33 -cd33
Page 1 and 2:
FM.fm Page i Friday, October 4, 200
Page 3 and 4:
FM.fm Page iii Friday, October 4, 2
Page 5 and 6:
FM.fm Page v Friday, October 4, 200
Page 7 and 8:
RehmanPaulTOC.fm Page vii Friday, O
Page 9 and 10:
RehmanPaulTOC.fm Page ix Friday, Oc
Page 11 and 12:
RehmanPaulTOC.fm Page xi Friday, Oc
Page 13 and 14:
RehmanPaulTOC.fm Page xiii Friday,
Page 15 and 16:
RehmanPaulTOC.fm Page xv Friday, Oc
Page 17 and 18:
Preface.fm Page xvii Wednesday, Oct
Page 19 and 20:
Preface.fm Page xix Wednesday, Octo
Page 21 and 22:
CH01.fm Page 1 Friday, October 4, 2
Page 23 and 24:
Page 25 and 26:
Page 27 and 28:
Page 29 and 30:
Page 31 and 32:
CH01.fm Page 11 Friday, October 4,
Page 33 and 34:
Page 35 and 36:
Page 37 and 38:
CH02.fm Page 17 Monday, October 7,
Page 39 and 40:
Page 41 and 42:
Page 43 and 44:
Page 45 and 46:
Page 47 and 48:
Page 49 and 50:
Page 51 and 52:
Page 53 and 54:
Page 55 and 56:
Page 57 and 58:
Page 59 and 60:
Page 61 and 62:
Page 63 and 64:
Page 65 and 66:
Page 67 and 68:
Page 69 and 70:
Page 71 and 72:
Page 73 and 74:
Page 75 and 76:
Page 77 and 78:
Page 79 and 80:
Page 81 and 82:
Page 83 and 84:
Page 85 and 86:
Page 87 and 88:
Page 89 and 90:
Page 91 and 92:
Page 93 and 94:
Page 95 and 96:
Page 97 and 98:
Page 99 and 100:
Page 101 and 102:
Page 103 and 104:
Page 105 and 106:
Page 107 and 108:
Page 109 and 110:
Page 111 and 112:
Page 113 and 114:
Page 115 and 116:
Page 117 and 118:
Page 119 and 120:
Page 121 and 122:
Page 123 and 124:
Page 125 and 126:
Page 127 and 128:
Page 129 and 130:
Page 131 and 132:
Page 133 and 134:
Page 135 and 136:
Page 137 and 138:
Page 139 and 140:
Page 141 and 142:
Page 143 and 144:
Page 145 and 146:
Page 147 and 148:
Page 149 and 150:
Page 151 and 152:
Page 153 and 154:
Page 155 and 156:
Page 157 and 158:
Page 159 and 160:
Page 161 and 162:
Page 163 and 164:
Page 165 and 166:
Page 167 and 168:
Page 169 and 170:
Page 171 and 172:
Page 173 and 174:
Page 175 and 176: CH05.fm Page 155 Monday, October 7,
Page 225: CH07.fm Page 205 Monday, October 7,
Page 277 and 278:
Page 279 and 280:
Page 281 and 282:
Page 283 and 284:
Page 285 and 286:
Page 287 and 288:
Page 289 and 290:
Page 291 and 292:
Page 293 and 294:
Page 295 and 296:
Page 297 and 298:
AppA.fm Page 277 Monday, October 7,
Page 299 and 300:
Page 301 and 302:
Page 303 and 304:
index.fm Page 283 Wednesday, Octobe
Page 305 and 306:
Page 307 and 308:
Page 309 and 310:
Page 311 and 312:
Page 313 and 314:
show all

The Linux Development Platform Configuring, Using, and ... - Classes

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?