Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!usc!jarthur!sburke
From: sburke@jarthur.Claremont.EDU (Scott Burke)
Newsgroups: comp.sys.handhelds
Subject: Re: Question about binary numbers and SAME  (HP-48)
Keywords: binary, SAME, Version E, bug
Message-ID: <10768@jarthur.Claremont.EDU>
Date: 12 Feb 91 01:20:44 GMT
References: <1991Feb9.185644.17146@nntp-server.caltech.edu> <59197@eerie.acsu.Buffalo.EDU>
Organization: Harvey Mudd College, Claremont, CA 91711
Lines: 13


But how do you deal with the analogous problem with unit objects, namely:

1_m DUP UBASE SAME yields a 0, not a 1, because for some reason the UBASE
argument is different.  I'm not into internals, but the same behavior is
occuring here, I think.  My (clumsy) solution was to do something along the
lines of { "'1_m'" } blah blah UBASE \->STR POS to check if I had the 
appropriate or desired unit.

Ideas on how to convert 1_m to 1_m?  ;-)

Scott.
sburke@jarthur.claremont.edu