Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!mnetor!seismo!nbires!isis!dragheb From: dragheb@isis.UUCP (Darius Ragheb) Newsgroups: comp.lang.c Subject: Re: draft ANSI standard: needs your tomatoes Message-ID: <1502@isis.UUCP> Date: Sat, 20-Dec-86 14:17:25 EST Article-I.D.: isis.1502 Posted: Sat Dec 20 14:17:25 1986 Date-Received: Sun, 21-Dec-86 03:56:47 EST References: <1384@hoptoad.uucp> <2550002@hpisod2.HP> Reply-To: dragheb@isis.UUCP (Darius Ragheb) Organization: Math/CS, University of Denver Lines: 22 Summary: don't support it, or do, but if you do, do it right In article <2550002@hpisod2.HP> decot@hpisod2.HP (Dave Decot) writes: >> The constants EXTERNAL_NAME_LENGTH (6), INCLUDE_FILES_NEST >> (4), and SOURCE_LINE_LENGTH (509) in particular seem to be very >> object to the ANSII committee approving of this limitation. > >maximum length of *each* source line. Personally, I'd like to see that >particular value set to 128, so I can fit listings on my lineprinter. > Hmm. Why not just stick to the zero, one, infinite principle: if you are going to support something (like the length of a line (:-) or the nesting levels), why, either allow one level, or an infinite number (obviously there will be an upper limit, probably machine dependant that will never be reached, but why build an upper limit that is some arbitrary number like 4 or 6.... that is as bad as the old FORTRAN limit of 7 dimensions for an array.... where did that number come from?) -- Functionality, Efficiency, Luxury. isis!dragheb | dragheb@isis.cs.du.edu