Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!sol.ctr.columbia.edu!emory!gatech!purdue!haven!adm!smoke!gwyn
From: gwyn@smoke.brl.mil (Doug Gwyn)
Newsgroups: comp.std.c
Subject: Re: comment style
Message-ID: <15088@smoke.brl.mil>
Date: 5 Feb 91 20:07:51 GMT
References: <4423@alliant.Alliant.COM> <-286619997@hpcupt1.cup.hp.com>
Organization: U.S. Army Ballistic Research Laboratory, APG, MD.
Lines: 11

In article <-286619997@hpcupt1.cup.hp.com> jamiller@hpcupt1.cup.hp.com (Jim Miller) writes:
>Granted, there might be cases where // might be in a literal, but
>a quick look with fgrep should find those for you and then take additional
>action (in a awk script).
>O.K., so what am I so stupid that I'm not seeing?

// may also be in a /*...*/ comment.

I once wrote a utility to de-// such source code; it implemented an FSA
and had something like twenty states as I recall.  It wasn't trivial but
it also wasn't all that difficult.