Return-Path: Received: by snark.thyrsus.com (/\==/\ Smail3.1.21.1 #21.19) id ; Fri, 7 Feb 92 18:50 EST Received: by cbmvax.cbm.commodore.com (5.57/UUCP-Project/Commodore 2/8/91) id AA01521; Fri, 7 Feb 92 18:05:22 EST Received: from rutgers.edu by relay2.UU.NET with SMTP (5.61/UUNET-internet-primary) id AA09898; Fri, 7 Feb 92 14:59:31 -0500 Received: from cbmvax.UUCP by rutgers.edu (5.59/SMI4.0/RU1.4/3.08) with UUCP id AA00840; Fri, 7 Feb 92 11:35:55 EST Received: by cbmvax.cbm.commodore.com (5.57/UUCP-Project/Commodore 2/8/91) id AA02782; Fri, 7 Feb 92 11:14:01 EST Received: from CUVMB.COLUMBIA.EDU (via uunet.UU.NET) by relay1.UU.NET with SMTP (5.61/UUNET-internet-primary) id AA05692; Fri, 7 Feb 92 10:56:06 -0500 Message-Id: <9202071556.AA05692@relay1.UU.NET> Received: from CUVMB.COLUMBIA.EDU by CUVMB.COLUMBIA.EDU (IBM VM SMTP R1.2.1) with BSMTP id 5689; Fri, 07 Feb 92 10:54:57 EST Received: by CUVMB (Mailer R2.07) id 4087; Fri, 07 Feb 92 10:53:47 EST Date: Fri, 7 Feb 1992 15:33:09 +0000 Reply-To: And Rosta Sender: Lojban list From: And Rosta Subject: Re: Digit strings To: John Cowan In-Reply-To: (Your message of Tue, 04 Feb 92 08:39:54 EST.) <3930.9202051327@ucl.ac.uk Status: RO X-From-Space-Date: Fri Feb 7 18:50:59 1992 X-From-Space-Address: cbmvax!uunet!cuvma.bitnet!LOJBAN Given Lojban's kill-one-bird-with-many-stones principle, I wonder whether the option of listing digits in order of increasing magnitude has been considered. I.e. 1,234,567,890 comes out as 0987654321. The disadvantage with this is you don't know how big the number is going to get. But there could be some way of announcing its level of magnitude prior to listing the digits. Anyway, this solution is still needed even if digits are listed in decreasing magnitude, else you still have to wait to the end of the number before you know how big it is. The advantage of starting units first is you can compute the number as you go by a process of addition. Another disadvantage is where 'decimal' places go - my suggestion is only nice for integers. This seems like an area where it would be good for Lojban to provide constrained flexibility and let usage determine the preferred options. --- And