Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!uakari.primate.wisc.edu!aplcen!haven!adm!smoke!gwyn
From: gwyn@smoke.brl.mil (Doug Gwyn)
Newsgroups: comp.std.c
Subject: Re: Comment Syntax
Message-ID: <14390@smoke.brl.mil>
Date: 9 Nov 90 05:01:04 GMT
References: <HAGERMAN.90Nov7193212@rx7.ece.cmu.edu>
Organization: U.S. Army Ballistic Research Laboratory, APG, MD.
Lines: 14

In article <HAGERMAN.90Nov7193212@rx7.ece.cmu.edu> hagerman@ece.cmu.edu (John Hagerman) writes:
>Why didn't // ... newline comments make it into ANSI C?

They weren't in the base document, and one style of comment was deemed to
be sufficient.  (Note:  I once added support for this feature to the
Ritchie PDP-11 compiler that I maintained, and when a new non-PDP-11
computer was acquired just after I left, the staff at that company was
tasked with either hacking support for // comments into the new compiler
and indeed, into every future compiler they might have to use, or else
converting all the sources into normal C comment style.  Fortunately I
had left them with a utility for automatically performing such conversion,
based on an FSA.  (It was non-trivial, due to \, ', and " handling.)  Thus,
you know that I must like // comments, but on the other hand I learned a
lesson.)