Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!henry
From: henry@utzoo.UUCP (Henry Spencer)
Newsgroups: net.lang.c
Subject: Re: C needs BCD (ANSI People: Please Listen)
Message-ID: <4558@utzoo.UUCP>
Date: Tue, 30-Oct-84 15:20:27 EST
Article-I.D.: utzoo.4558
Posted: Tue Oct 30 15:20:27 1984
Date-Received: Tue, 30-Oct-84 15:20:27 EST
References: <218@x.UUCP> <163@desint.UUCP>, <229bf5db.8e4@apollo.uucp>
Organization: U of Toronto Zoology
Lines: 15
Keywords: BCD, floating, types /

> I think implementing BCD like strings would NOT be a good idea.  People
> who use it will want to use it just like any other type, and I don't think
> that's unreasonable.

People who use strings would like to use them just like any other type,
and this is an eminently reasonable request.  The point is, it's hard.
How long are strings?  How are they allocated?  What happens when they
overflow?  How can you define an adequate set of string operators and
still keep the complexity down?  Most of these questions apply, with
equal strength, to BCD.  Remember, "BCD" does *not* denote a single type;
BCD of *what* *length*?  Building in a whole family of numeric types
is not a decision to be taken lightly; that way lies Ada...
-- 
				Henry Spencer @ U of Toronto Zoology
				{allegra,ihnp4,linus,decvax}!utzoo!henry