Path: utzoo!utgpu!watserv1!watmath!att!att!linac!pacific.mps.ohio-state.edu!zaphod.mps.ohio-state.edu!lavaca.uh.edu!menudo.uh.edu!sugar!ficc!peter From: peter@ficc.ferranti.com (Peter da Silva) Newsgroups: comp.std.c Subject: Re: Comment Syntax Message-ID: Date: 19 Nov 90 22:15:44 GMT References: <14390@smoke.brl.mil> <48.UUL1.3#5077@aussie.COM> <1990Nov16.172018.19638@zoo.toronto.edu> Reply-To: peter@ficc.ferranti.com (Peter da Silva) Organization: Xenix Support, FICC Lines: 12 In article <1990Nov16.172018.19638@zoo.toronto.edu> henry@zoo.toronto.edu (Henry Spencer) writes: > The intent is that it be possible to split lines mechanically, e.g. to deal > with machines with stupid line-length limits, and hence it is desirable to > have backslash-newline processing first so that you don't have to tokenize > the source to decide where line breaks are safe. Ok, that makes sense. Well in that case what's the problem with // .... .... \ .... ... being a comment? If /\ * ... .... ... */ is accepted, anything goes... -- Peter da Silva. `-_-' +1 713 274 5180. 'U` peter@ferranti.com