Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!ub!acsu.buffalo.edu
From: cloos@acsu.buffalo.edu (James H. Cloos)
Newsgroups: comp.sys.handhelds
Subject: Re: More explorations...(HP48)
Message-ID: <68956@eerie.acsu.Buffalo.EDU>
Date: 4 Apr 91 21:15:22 GMT
References: <36F537C380002DD9@gacvx2.gac.edu>
Sender: news@acsu.Buffalo.EDU
Organization: State University of New York @ Buffalo
Lines: 25
Nntp-Posting-Host: lictor.acsu.buffalo.edu

In article <36F537C380002DD9@gacvx2.gac.edu> CW%APG.PH.UCL.AC.UK@pucc.PRINCETON.EDU writes:
>             #5A03h SYSEVAL converts a binary on the stack to a system binary
>             #      SYSEVAL converts a real on the stack to a system binary
>
#18CEAh does the real->system_binary

>                         2:             <2h>  <-  Is this the third dimension?
>                         1:          { 2 2 }
Yes, that is the first dimention.  Obviously the routine that returns the
dimentions of an array (returning system_binaries) is smart enough to
handle n-dimentional arrays; unfortunately, all that is checked is if 1
value was returned or if more than 1 value was returned, in the latter
case, either the routine "list-> drop sb->r swap sb->real swap 2 >list", in
some form, or "sb->r swap sb->r swap 2 >list", in some form, is executed.
(I dan't know offhand whether the values are returned as a list or a
meta-object.)  That is why the extra sys_bin is left on the stack.
(NB: this is all from my explorations, and is really a theory--a bit better
than just a hypothesis, I should think--don't take this as authoritative.)

-JimC
--
James H. Cloos, Jr.		Phone:  +1 716 673-1250
cloos@ACSU.Buffalo.EDU		Snail:  PersonalZipCode:  14048-0772, USA
cloos@ub.UUCP			Quote:  <>