rhoward@msd.gatech.edu (Robert L. Howard) (07/13/90)
When using cpp to process the source to a script file, cpp always puts a blank line in the output for everytime it encounters a #directive or a /*comment*/. (This is SunOS 4.1) Is this normal behavior? If so, why? It really makes the resulting shell script messy with all those blank lines... My manual suggests m4 as an alternative but I'm not sure it won't do the same thing. More importantly, this is a X11 shell script with an Imakefile with all the predefined rules pointing to cpp already. If m4 is the correct choice, why didn't MIT choose to use it? Inquiring minds want to know.... Thanks, Robert -- | Robert L. Howard | Georgia Tech Research Institute | | rhoward@msd.gatech.edu | MATD Laboratory | | (404) 528-7165 | Atlanta, Georgia 30332 | | UUCP: ...!{allegra,amd,hplabs,ut-ngp}!gatech!msd!rhoward |
jimf@SABER.COM (07/13/90)
|When using cpp to process the source to a script file, cpp always |puts a blank line in the output for everytime it encounters a |#directive or a /*comment*/. (This is SunOS 4.1) Is this normal |behavior? If so, why? Yes. It makes it easier to keep the line counter in sync with reality. |It really makes the resulting shell script |messy with all those blank lines... cpp | cat -s |My manual suggests m4 as an alternative [...] |If m4 is the correct choice, why didn't MIT choose to use it? I wouldn't use it because it's not guaranteed to be on every platform. jim frost saber software jimf@saber.com
guy@auspex.auspex.com (Guy Harris) (07/15/90)
>|If m4 is the correct choice, why didn't MIT choose to use it? > >I wouldn't use it because it's not guaranteed to be on every platform. Neither is "cpp"....