Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!dimacs.rutgers.edu!mips!sdd.hp.com!hp-pcd!hpcvra.cv.hp.com!rnews!hpcvbbs!akcs.waterman
From: akcs.waterman@hpcvbbs.UUCP (Jason Todd Waterman)
Newsgroups: comp.sys.handhelds
Subject: Re: Matrix Writer
Keywords: implementing inside programs? (mat. wrt.)
Message-ID: <27defe95:2377.1comp.sys.handhelds;1@hpcvbbs.UUCP>
Date: 14 Mar 91 05:40:05 GMT
References: <27db3149:2377comp.sys.handhelds@hpcvbbs.UUCP>
Lines: 27

This problem can be solved by executing a SYSEVAL for the
{Blue-shift}{ENTER} key.  The address for this is #3B068h.  A sample
program for executing the MATRIXWRITER and then storing the result in a
user defined variable would look like this:

<< #3B068h SYSEVAL 'TEST' STO >>

This assumes that the user did not exit the matrix writer using the ATTN
key.  If that was the case, you would have to check that there was
actually something returned to the stack.  One way to check would be to
determine if the object returned was an array.  For example:

<<  0                    @Places a non array object on stack just
    #3B068h SYSEVAL      @in case you are using other arrays in your
    DUP                  @program.
    IF TYPE 3 SAME       @Check object type.  If it is a real array
    THEN 'TEST' STO      @then store it in variable 'TEST'.
    END DROP >>          @Drop the 0.

If you will be entering complex arrays then you must modify the program
to check for object type 4 as well.  Sorry if this doesn't quite make
sense, but I'm making it up in my head as I go along.  Hope this helps
solve your problem!

Jason Waterman
The University of Calgary
Calgary, Alberta, Canada
Email: waterman@engg.ucalgary.ca