Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.1 6/24/83; site umcp-cs.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!allegra!mit-eddie!godot!harvard!seismo!umcp-cs!chris
From: chris@umcp-cs.UUCP (Chris Torek)
Newsgroups: net.bugs.4bsd,net.unix-wizards
Subject: Re: bug fixes for talk
Message-ID: <1879@umcp-cs.UUCP>
Date: Fri, 14-Dec-84 10:34:03 EST
Article-I.D.: umcp-cs.1879
Posted: Fri Dec 14 10:34:03 1984
Date-Received: Sun, 16-Dec-84 05:11:58 EST
References: <2547@sdcc3.UUCP>
Distribution: net
Organization: U of Maryland, Computer Science Dept., College Park, MD
Lines: 16
Xref: watmath net.bugs.4bsd:1290 net.unix-wizards:11067

AARRGH!

*Why* must 90% of the people who "fix" talk use Vax byte order?  Talk
uses UDP; UDP is an *Internet* protocol; there is a *STANDARD* for this
kind of stuff!  Try using ntohl/htonl and ntohs/htons to use *standard
network* byte order.  Then your program will work on *any* new 4.2 Unix
machines, no matter what their internal integer formats are.

(Of course it's not really the fault of people "fixing" talk, it's
the fault of whoever wrote talk wrong in the first place....)
-- 
(This line accidently left nonblank.)

In-Real-Life: Chris Torek, Univ of MD Comp Sci Dept (301) 454-7690
UUCP:	{seismo,allegra,brl-bmd}!umcp-cs!chris
CSNet:	chris@umcp-cs		ARPA:	chris@maryland