Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!ccu.umanitoba.ca!herald.usask.ca!alberta!ubc-cs!fs1!hershey.ee.ubc.ca!jmorriso
From: jmorriso@hershey.ee.ubc.ca (John Paul Morrison)
Newsgroups: comp.sys.handhelds
Subject: Re: HP48 compact arrays
Message-ID: <1521@fs1.ee.ubc.ca>
Date: 13 Feb 91 22:03:33 GMT
References: <5966@hplabsb.HP.COM> <27b4e2a1:1997.2comp.sys.handhelds;1@hpcvbbs. <27b83c55:1997.3comp.sys.handhelds;1@hpcvbbs.UUCP> <7264@uqcspe.cs.uq.oz.au>
Sender: root@fs1.ee.ubc.ca
Reply-To: jmorriso@hershey.ee.ubc.ca (John Paul Morrison)
Organization: Dept. of Electrical Engineering University of B.C.
Lines: 9

If people are worried about users inadvertently accessing data stored in
a code, string, or binary object, any object can be hidden inside a library data
object. Library data objects can't be edited, or accidentally modified. They
show up as "Library Data" on the stack, so that is less confusing to a user,
than "Array of String".

If you unthread the PTpar variable, you will see it only has a string inside.
The MHpar variable contains a list which has a GROB, a string, and some Sytem
Binaries inside.