Xref: utzoo comp.sys.next:18524 comp.bugs.4bsd:1822 comp.mail.uucp:6785
Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!hplabs!nsc!pyramid!salt!romain
From: romain@salt.pyramid.com (Romain Kang)
Newsgroups: comp.sys.next,comp.bugs.4bsd,comp.mail.uucp
Subject: Re: Bug in uuq on NeXT -- cannot change baudrate
Message-ID: <158300@pyramid.pyramid.com>
Date: 5 Jun 91 22:13:26 GMT
References: <1991Jun4.202736.3158@shaman.com>
Sender: news@pyramid.pyramid.com
Reply-To: romain@pyramid.com
Lines: 15

In <1991Jun4.202736.3158@shaman.com> jiro@shaman.com (Jiro Nakamura) writes:
| 	The bug is caused by one line in uuq.c (lines 130-132):
|                case 'b':
|                         baudrate = atof(optarg);
|                         break;

The original 4.3 uuq source declared atof() as float.  It's really a
double, but VAXen don't care.  It was fixed in 4.3-tahoe.

Clearly, using atoi() works also.  Lou Salkind may have automatically
used atof() because (if I recall correctly) he was a graduate physics
student at the time.
--
``!!x09 dimaryP a fo edisni deppart m'I !pleH''
``oNhwre eenraa  sab dsab iegnt arppdei  n aAV X117/05!!''