Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!rutgers!ucla-cs!admin.cognet.ucla.edu!casey
From: casey@admin.cognet.ucla.edu (Casey Leedom)
Newsgroups: comp.sys.apollo
Subject: Re: /usr/lib/cpp has trouble outputting long lines??
Keywords: /usr/lib/cpp, X.V11R2, imake
Message-ID: <15688@shemp.CS.UCLA.EDU>
Date: 1 Sep 88 09:55:46 GMT
References: <15567@shemp.CS.UCLA.EDU> <3e3050a4.12edf@apollo.COM>
Sender: news@CS.UCLA.EDU
Reply-To: casey@cs.ucla.edu (Casey Leedom)
Organization: none
Lines: 21

In article <3e3050a4.12edf@apollo.COM> pato@apollo.COM (Joe Pato) writes:
> The sr9.7 /usr/lib/cpp intentionally breaks long lines.  This facility
> was provided to avoid the problem that the 9.7 C compiler had with
> reading input lines longer than 256 characters.

  This isn't an acceptable answer.  Your compiler was broken, so you
broke cpp also???  Your compiler doesn't even use /usr/lib/cpp for the
most part!!!  At the *VERY* least, provide a switch to cpp to get it to
give me unbroken output lines.

  It took me over an hour to get the standard cpp from Berkeley compiled
and working correctly.  I had access to that source.  What would someone
who didn't have access to that source do???  And where is the
documentation of your change?  I don't see it in the cc manual page.

  What is it?  You think you can change anything in Unix randomly and
still call what you end up with Unix?  Get off it.  That's not customer
support.  (And this isn't Unix - let's all hear it for ... `fixed in
SR10' ...)

Casey