Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!usc!zaphod.mps.ohio-state.edu!ncar!noao!arizona!dave
From: dave@cs.arizona.edu (Dave P. Schaumann)
Newsgroups: comp.std.c
Subject: Re: comment style
Message-ID: <628@caslon.cs.arizona.edu>
Date: 9 Jan 91 13:59:26 GMT
References: <1991Jan04.164355.15674@sco.COM> <613@caslon.cs.arizona.edu> <1050:Jan701:40:4791@kramden.acf.nyu.edu> <616@caslon.cs.arizona.edu> <1991Jan08.192415.3361@grep.co.uk>
Organization: U of Arizona CS Dept, Tucson
Lines: 23

In article <1991Jan08.192415.3361@grep.co.uk> frank@grep.co.uk (Frank Wales) writes:
|In article <616@caslon.cs.arizona.edu| dave@cs.arizona.edu (Dave P. Schaumann)
| writes:
||In article <1050:Jan701:40:4791@kramden.acf.nyu.edu| 
|| brnstnd@kramden.acf.nyu.edu (Dan Bernstein) writes:
|||4. It is always obvious, to both human eye and mechanical parser, where
|||a // comment ends (viz., the end of the line). It is not so trivial to
|||locate the next */.
||
||My editor has a 'search for text' function.  Doesn't yours?
|
|My editor doesn't have a 'search for text in printouts' function.  Does yours?

Actually, I considered this point when I was making the original post.  The
reason I decided it wasn't important is that I can't imagine doing any serious
work on a program when only hardcopy is available.  (*Surely* there is an
on-line copy somewhere!)

|Frank Wales, Grep Limited,             [frank@grep.co.uk<-|uunet!grep!frank]
|Kirkfields Business Centre, Kirk Lane, LEEDS, UK, LS19 7LX. (+44) 532 500303

Dave Schaumann		| My folks went to uunet.uu.net, but all
dave@cs.arizona.edu	| they got me was this lousy .sig...