Path: utzoo!utgpu!attcan!lsuc!eci386!jmm
From: jmm@eci386.uucp (John Macdonald)
Newsgroups: comp.lang.c++
Subject: Re: C++ Comments
Message-ID: <1989May26.154829.1616@eci386.uucp>
Date: 26 May 89 15:48:29 GMT
References: <6957@brunix.UUCP> <7636@saturn.ucsc.edu>
Reply-To: jmm@eci386.UUCP (John Macdonald)
Organization: R. H. Lathwell Associates: Elegant Communications, Inc.
Lines: 20

In article <7636@saturn.ucsc.edu> easterb@ucscb.UCSC.EDU (William K. Karwin) writes:
|In article <6957@brunix.UUCP> sdm@cs.brown.edu (Scott Meyers) writes:
|>Consider the following C++ source line:
|>
|>    //**********************
|>
|
|...         We think one way to solve it is to have in a makefile:
|
|.c.o:
|	@sed s/\\/\\/.\*// $< > $*.C
|	CC $(CFLAGS) -c $*.C
|	@/bin/rm -f $*.C

This will cause rare and therefore surprising problems whenever a program
has a string containing // (for example, generator programs for: ed scripts
(or any other generating programs that use pattern matches, sed, perl, ...);
JCL (did I really admit that I thought of that example?); checks for doubled
slashes in pathnames generated by concatenating a bunch of strings).