This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: aggressive fixincludes
- To: Joe Buck <jbuck at synopsys dot COM>
- Subject: Re: aggressive fixincludes
- From: Andreas Schwab <schwab at suse dot de>
- Date: 24 Nov 1999 19:20:48 +0100
- Cc: ddsinc09 at ix dot netcom dot com, gcc at gcc dot gnu dot org, mark at codesourcery dot com,autogen at linuxbox dot com
- References: <199911241731.JAA10342@atrus.synopsys.com>
Joe Buck <jbuck@synopsys.COM> writes:
|> > At the same time, I do not think it crucial that the comments
|> > remain. After all, they _are_ comments and /usr/include/FlexLexer.h
|> > still remains in /usr/include for visual reference. Please,
|> > propose a solution.
|>
|> What's wrong with
|>
|> sed 's?//\(.*\)?/*\1*/?' file > new_file
|> ?
|>
|> For those like me who find regular expressions to be write-only,
|> that means change
|> // anything
|> to
|> /* anything*/
What if `anything' contains `*/'?
--
Andreas Schwab "And now for something
SuSE Labs completely different."
schwab@suse.de
SuSE GmbH, Schanzäckerstr. 10, D-90443 Nürnberg