Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watmath!clyde!rutgers!ames!ptsfa!ihnp4!cuae2!ltuxa!ttrdc!levy
From: levy@ttrdc.UUCP
Newsgroups: comp.lang.c
Subject: Re: Distinguished pointers (was Re: Weird syscall returns)
Message-ID: <1847@ttrdc.UUCP>
Date: Mon, 10-Aug-87 23:00:38 EDT
Article-I.D.: ttrdc.1847
Posted: Mon Aug 10 23:00:38 1987
Date-Received: Thu, 13-Aug-87 01:23:42 EDT
References: <1158@copper.TEK.COM> <6858@auspyr.UUCP> <17171@cca.CCA.COM> <6242@brl-smoke.ARPA>
Organization: AT&T, Skokie, IL
Lines: 23

In article <6242@brl-smoke.ARPA>, gwyn@brl-smoke.ARPA (Doug Gwyn ) writes:
< In article <5193@utcsri.UUCP> flaps@utcsri.UUCP (Alan J Rosenthal) writes:
< -    case '\n':
< -#ifndef OS9
< -    case '\r':
< -is WRONG.  The test line should be:
< -#if '\n' != '\r'
< 
< It's all wrong anyway -- in C, '\r' and '\n' represent distinct
< (whitespace) characters.

What is an implementation of C supposed to do on an OS/machine/character-code
combination that doesn't have the foggiest that there is such a thing
as distinct "new line" and "carriage return" characters?  From the looks of
the discussion here, I'd gather that OS9 is just such a beast and its C
compiler is making the best of this brain damaged situation that it can.

[Or perhaps, as Guy Harris likes to say, it "ain't C." :-) ]
-- 
|------------Dan Levy------------|  Path: ..!{akgua,homxb,ihnp4,ltuxa,mvuxa,
|         an Engihacker @        |		vax135}!ttrdc!ttrda!levy
| AT&T Computer Systems Division |  Disclaimer:  i am not a Yvel Nad
|--------Skokie, Illinois--------|