Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!iuvax!cica!tut.cis.ohio-state.edu!zaphod.mps.ohio-state.edu!think!mintaka!oliveb!amdahl!rtech!llama!glenk
From: glenk@llama.rtech.UUCP (Glen Kilpatrick)
Newsgroups: comp.sys.handhelds
Subject: Want HP-28S fuel gauge, program name query
Message-ID: <4374@rtech.rtech.com>
Date: 28 Dec 89 12:40:32 GMT
Sender: news@rtech.rtech.com
Reply-To: glenk@llama.UUCP (Glen Kilpatrick)
Organization: Relational Technology, Inc. Alameda, CA
Lines: 26


Please put on your thinking caps, 28S_chums, and tell me if anyone's
had a glimmer of an idea re these two modest problems:

*  What about a "fuel gauge" for the 28?  I'd like a function that
would return a real number between 0 & 1 indicating battery voltage,
where 1 = new batteries, & 0 means the low-battery indicator was
just triggered.  If it could report hours of continuous computation
left, it would be a googol times GREATER (but that's too much to
hope for!)!

*  I keep a "catalog" of ~150 objects of the form << param1 param2
pgm >> 'name1' STO.  I'd like pgm to report "Output for name1" when
it executes, but cannot afford the MEM to encode name1 INSIDE name1.
So, is there a way for an executing program to know its own name,
and the names of its "shell" programs?  Of course, programs executed
from the stack could not have a name (unless it was "1", since they
could only be executed from level 1, a la 1_visit), but there MIGHT
be a way for global/local variables.

Please be cautious re SYSEVALs in your answers.  I crashed my sys
last week, and took over a day to type all back in, so I'd prefer
rugged/tested implementations.  Thanks!

						Glen Kilpatrick
                                                (916)756-9321home