Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84; site brl-tgr.ARPA
Path: utzoo!linus!decvax!genrad!panda!talcott!harvard!seismo!brl-tgr!tgr!jeff@isi-vaxa.ARPA
From: jeff@isi-vaxa.ARPA (Jeffery A. Cavallaro)
Newsgroups: net.lang.c
Subject: EOL WAR
Message-ID: <1296@brl-tgr.ARPA>
Date: Fri, 6-Sep-85 16:49:16 EDT
Article-I.D.: brl-tgr.1296
Posted: Fri Sep  6 16:49:16 1985
Date-Received: Tue, 10-Sep-85 20:27:38 EDT
Sender: news@brl-tgr.ARPA
Lines: 22

HOLD IT, HOLD IT !!!

Sorry to start such a war by suggesting:

#define		EOL		'\0'

I had used this definition a couple of times when manipulating text coming
from human-type interfaces (i.e. computer control of human interfaces).
Programs fielding input from such interfaces must not depend on the presence
of format characters (e.g. \n or \r) because these human interfaces are very
loose and dynamic from version to version.  While manipulating such "lines"
of text, I would remove format characters and terminate the string with an
EOL (\0).

#define		EOS		'\0'
#define		EOL		'\n'

These are not wrong, but \n as EOL has a bad taste when dealing with such
interfaces.  They are fine as long as you stay within the VAX-11 4.2BSD
(or similar) environment.

					Jeff