Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!ukma!xanth!lll-winken!uunet!portal!cup.portal.com!Tim_CDC_Roberts
From: Tim_CDC_Roberts@cup.portal.com
Newsgroups: comp.lang.c
Subject: Re: Want a way to strip comments from a
Message-ID: <16078@cup.portal.com>
Date: 21 Mar 89 17:20:59 GMT
References: <7150@siemens.UUCP> <9900010@bradley> <4896@cbnews.ATT.COM> <3145@nunki.usc.edu> <3163@nunki.usc.edu>
Distribution: na
Organization: The Portal System (TM)
Lines: 15

You know, this discussion has brought up something that has bothered me
(although not a great deal).

When scanning the result of preprocessing a nontrivial C program with 
many include files, one finds dozens (in some cases hundreds) of blank
lines.  Obviously, they are the result of eliminating preprocessor
directives and multiline comments.  What I have always wondered is why,
given the #line directive which can re-sync the preprocessor and the
compiler, does the preprocessor insist on keeping all those blank lines?
Why not eliminate them and issue a #line instead?

Just curious.

Tim_CDC_Roberts@cup.portal.com                | Control Data...
...!sun!portal!cup.portal.com!tim_cdc_roberts |   ...or it will control you.