Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!rutgers!sri-unix!hplabs!sdcrdcf!markb
From: markb@sdcrdcf.UUCP (Mark Biggar)
Newsgroups: comp.lang.c
Subject: Re: draft ANSI standard: needs your tomatoes
Message-ID: <3496@sdcrdcf.UUCP>
Date: Fri, 5-Dec-86 12:05:01 EST
Article-I.D.: sdcrdcf.3496
Posted: Fri Dec  5 12:05:01 1986
Date-Received: Sun, 7-Dec-86 21:28:26 EST
References: <1384@hoptoad.uucp> <5421@brl-smoke.ARPA> <1155@ucbcad.BERKELEY.EDU>
Reply-To: markb@sdcrdcf.UUCP (Mark Biggar)
Organization: System Development Corporation R&D, Santa Monica
Lines: 15

In article <1155@ucbcad.BERKELEY.EDU> faustus@ucbcad.BERKELEY.EDU (Wayne A. Christopher) writes:
>(4), and SOURCE_LINE_LENGTH (509) in particular seem to be very
>...
>excuse not to fix their compilers?  A compiler that won't accept a
>600-line input file is clearly sub-standard and almost useless, and I

SOURCE_LINE_LENGTH is the length of 1 line of input (i.e., the number of
chars between newlines) not the number of line in the input file.
I believe the 509 comes from taking 512 (2**9) and taking away the end of
line sequence which can, on some machines, be as much as 3 chars long (e.g.,
the DEC RSTS system that has 3 different line terminating sequences,
"\027" "^[", "\015\012" "\r\n" and "\012\015\000" "\n\r\0".)

Mark Biggar
{allegra,burdvax,cbosgd,hplabs,ihnp4,akgua,sdcsvax}!sdcrdcf!markb