Path: utzoo!utgpu!water!watmath!clyde!rutgers!rochester!cornell!uw-beaver!mit-eddie!husc6!cmcl2!brl-adm!brl-smoke!gwyn
From: gwyn@brl-smoke.ARPA (Doug Gwyn )
Newsgroups: comp.lang.c
Subject: Re: Say what!?  (Re: MSC 5.0 Bug Fix?? (Simple..))
Message-ID: <7303@brl-smoke.ARPA>
Date: 21 Feb 88 11:17:17 GMT
References: <11739@brl-adm.ARPA> <1988Feb17.171813.15472@utzoo.uucp> <2183@ttrdc.UUCP>
Reply-To: gwyn@brl.arpa (Doug Gwyn (VLD/VMB) <gwyn>)
Organization: Ballistic Research Lab (BRL), APG, MD.
Lines: 14

In article <2183@ttrdc.UUCP> levy@ttrdc.UUCP (Daniel R. Levy) writes:
>Ahem, what does X3J11 have to say about source files on systems (like VMess)
>that support "record" text files?

Why should X3J11 have to say anything about this?  It is the job of
the implementor to meet the specs.  In fact this particular problem
has been solved many times already by C compiler vendors.

Note that the implementor only has to provide one form of text stream
and one form of binary stream; other file formats could be handled as
extensions.  Most vendors are likely to do whatever they can to support
as many file types as possible, because it will make their customers
happier.  On VMS, for example, RMS can be used to help map strange file
types into a smaller number of regular models.