Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!gatech!bloom-beacon!eru!hagbard!sunic!mcsun!hp4nl!charon!jurjen
From: jurjen@cwi.nl (Jurjen NE Bos)
Newsgroups: comp.sys.handhelds
Subject: Re: 32 Bt Mant is < I need!
Message-ID: <2667@charon.cwi.nl>
Date: 10 Dec 90 12:31:21 GMT
References: <276057f4:1381comp.sys.handhelds@hpcvbbs.UUCP> <1990Dec10.034626.27415@cc.ic.ac.uk> <10060@jarthur.Claremont.EDU>
Sender: news@cwi.nl
Lines: 27

bgribble@jarthur.Claremont.EDU (Bill Gribble) writes:

>In article <1990Dec10.034626.27415@cc.ic.ac.uk> umapd51@cc.ic.ac.uk (W.A.C. Mier-Jedrzejowicz) writes:
>>
>It might be an interesting (if overly complex) project to try to implement
>  extended-precision math functions in machine language.  You would
>  have to hack a new type for entry and display - say, a string with the 
>  first character a # or somesuch.  But you could do arbitrarily high
>  precision math.  Left as an exercise for the reader :-)  

No! You don't!  The 48SX already has arbitrary-large binaries--except that
it cannot do computations with them.  The display routines can show
binaries of any size in the style
	C# <number of digits> <digits in reverse order hex>
but you cannot enter them.

If you want to see some of those numbers, look in the hidden directory (the
one with the empty name) and look in your alarm catalog.  Alarms are stored
like { B E } where B is a 24 nibble binary storing the date, time and
repeat interval, and E is the EXEC.
(For the nosy ones: this binary stores the value of TICKS of the time and
date of the alarm, prepeded by the number of ticks between to repetitions
of the alarm.  Funny format.  This list {B E} can be converted to RCLALARM
format with #E1D8 SYSEVAL, if I'm not mistaken.)

If only someone would write input and calculation routines for those
long binaries...