Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!mcnc!duke!zodiac.phy.duke.edu!dcf
From: dcf@zodiac.phy.duke.edu
Newsgroups: comp.sys.handhelds
Subject: HP48SX units comparison problem
Message-ID: <21625@duke.cs.duke.edu>
Date: 28 Sep 90 18:26:22 GMT
Sender: news@duke.cs.duke.edu
Reply-To: dcf@zodiac.phy.duke.edu ()
Distribution: usa
Organization: Duke University Physics Dept.; Durham, N.C.
Lines: 30
Nntp-Posting-Host: zodiac.phy.duke.edu

Units comparison problem: SAME doesn't behave consistently with units objects.
Consider the following:

<< '1_m' '1_m' DUP2 SAME 3 ROLLD == >>

This returns:

2:  1
1:  1

But

<< '1_m' UBASE '1_m' DUP2 SAME 3 ROLLD == >>

returns:

2:  0
1:  1

It appears that UBASE tags an object in some invisible way. When I do a
MEMORY BYTES on a plain 1_m and a UBASE 1_m I get different answers.

plain 1_m:      #D2FCh              UBASE 1_m:      #E983h
                16                                  12.5

Naturally, I want to avoid the "b" word, but what is going on here?
--
	Daniel C. Flatin			1-919-684-8279
	Duke University Dept. of Physics	def@phy.duke.edu
	Durham, N.C.      27706