RPLLAB v1.0 copyright (C) 1998 Yale Kozinski (for the time being...)
yalek@geocities.com
Please tell me about any bugs/problems with this program!  Thank you!

RPLLAB is designed to simplify converting QBASIC programs to USER-RPL
Basically (no pun intended) it takes a mostly converted RPL program,
scans it for specific keywords, and uses tricky methods to output an
"installation program," which when run on an HP48 will create several
other programs with names defined by the programmer.  This is only
a very preliminary version!  I haven't exactly tested it under every
rigourous situation, so please don't blame me if it makes your calc die!
I advise you to back up your calculator before using this program, although
given that it only adds one syseval, #6FD1h SYSEVAL, which is the COLA
command, it shouldn't have too many ill effects ( I hope :-) ).

Syntax: RPLLAB.EXE infile outfile main_function_name
infile and outfile are obviously the input file and the output file
main_function_name is the label that you want to give the first function,
that is to say, what you would call the program if it were only one file.
This is also the label given to the start of the program.

Inside the program:

GLABEL label
This defines a label, obviously.
GOTOGL label
This transfers control to the specified label, via use of the sysrpl COLA
command (Is there a better way to do this anyone?)

If you just put the name of the label, it will call it just like a subroutine
I suppose you could simulate GOSUB with creative use of the SEMI command.
I would like to incorporate this into a later version, so, again, does anyone
know of a better way to do this?

Remember though:

Do not put a GLABEL within a secondary set of program delimiters ( \<< \>> )
i.e. none of this:
\<<
1 2 \->
\<<
GLABEL blah
\>>
\>>
And don't put any GLABEL's within loop delimiters either.
It makes for useless output :-)

RPLLAB puts an endline after each command in your original program.  I hope this is
not too much of a problem for anyone, but you can always change it later
anyhow.

You should probably run the "installer" in it's own directory, as it creates
quite a few variables (one for each label).

If anyone wants to modify the C++ source, go right ahead, but please send it
to me at yalek@geocities.com so I can see what you did.  Thank you.

