All files in the RPL48 kit are copyrighted (c) by Detlef Mueller and Raymond
Hellstern, 1999 -- unless otherwise noted.

The RPL48 kit is distributed in the hope that it will be fun, but RPL48 is
provided `as is,' and is subject to change without notice.

D. Mueller and R. Hellstern make no warranty of any kind with regard to the
software or documentation, including, but not limited to, the implied
warranties of merchantability and fitness for a particular purpose.

D. Mueller and R. Hellstern shall not be liable for any error or for incidental
or consequential damages in connection with the supply, performance, or use of
this software and documentation.

No part of the supplied sources may be reused in other projects without written
permission from D. Mueller or R. Hellstern. See RPL48.DOC, Appendix C for
contact information.

Permission to copy the whole, unmodified RPL48 package is granted provided that
the copies are not made or distributed for resale (excepting nominal copying
fees).

--------------------------------------------------------------------------------

The source of RPL48 3.0 consists of the following files:

\
    README		this file

\C			C sources of required helpers
    GENTAB   C		Source of the reference table generator
    STRIP    C		Source of the abs-lib strip program

\LIB			<-LIB->:2.3 source
    ENTRIES  H		Definitions of the unsupported entries used by <-LIB->
    LIB      S		Source of <-LIB->
    MKLIB    BAT	DOS job to build <-LIB->

\RPL			<-RPL->:5.1 source
    ENTRIES  H		Definitions of the unsupported entries used by <-RPL->
    KEYDEFS  H		Key definitions
    MKRPL    BAT	DOS job to build <-RPL->
    RPL-G    ASC	Source of a reference table (G/GX only)
    RPL      M		Linker definition file
    RPL      S		Source of <-RPL->
    RPL_42   H		Some common/macro definitions

After I bought my 1st '48 back in 1990 (rev. E SX), I (Detlef) thought myself
that the little gadget can do more than what was accessable to the user. So I
was looking for more information and checked a few companys in germany for
tools and documentation. That time, Raymond was working at WWW as a '48 pro-
programmer, just finishing the WWW Dis-/Assembler card and we got in contact.

So we started to develop RPL48 and the first public version was released in
mid 1991, the fully featured SX version was ready somewhen in 1992 and the GX
port in winter 1993. 'Till now, Raymond or I have finetuned the kit and it was
really fun to do it -- unfortunately that made the source some sort of home-
grown (you'll get the point when you examine it) and we'd have restructured it
if there wasn't a real life...

Because of the public availability of faster tools w/ more features (eg. JAZZ,
which, BTW, wasn't born w/o the existance of RPL48...), we decided to release
the source of RPL48 for learning/entertainment purposes -- it still contains a
lot never-seen-before tricks and its implementation is a class of its own
(IMHO).

We'll try to point you to the most interesting parts below.

Have fun,
	Detlef & Raymond
- -----------------------

Both libraries are designed as hybrids from different points of view, they are
made of mixed sRPL and assembler code (for a very good speed/size relation) and
both run on SX as well as on GX type machines.

<-LIB-> is (more or less) a "normal" designed library with the restriction of
beeing able to run from a covered port (ports 2-33 on a GX. This is because it
was initially written for the SX). Besides the code to build/split a library
and dealing w/ various "unsupported" but nevertheless build-in objects, there
are a few interesting routines:

  - EvalSG: is responsible for the S/G detection and for running the correct
    code (which is provided to it via the runstream)
  - DoVars is a very fast assembler replacement for the RPL word DOVARS
  - EqualPosComp is a very fast assembler replacement for the RPL word
    EQUALPOSCOM
  - {}- is the LISP list-list
  - STLIB is the routine that is able to store and activate a library w/o
    warmstarting the calc (jeez, that one took me weeks ;-)

Well, there're more, I'll leave the fun to you :-)

<-RPl-> is far away from beeing a "normal" library, it's written using the same
technics used in the '48s ROM based code (w/ the exception of its config code),
ie. the library is compiled to a fixed address (#C0000 to be exact).The reasons
for implementing it that way where speed and size,programing on fixed addresses
enables you to use some fancy methods like RPL GOTOs, assembler primitive
objects or elsewhere-prefixed objects. W/ the exception of the user visible
commands, there's no need to use ROMPTR, all internal RPL routines are just
LABELed. Some highlights to look at include:

  - mkrpl.bat, strip.c, rpl.m and the library layout in rpl.s (starting at
    ABS #C0000) -- all the stuff neccessary to make <-RPL-> absolut
  - RPLcfg is responsible for verifying the correct installation and more...
  - IsGX? is a good example for an elsewhere-prefixed object
  - GetToken uses GetNextToken to split RPL->'s input
  - Obj? is a PCO, it's the inner RPL decompiler dispatcher does interesting
    things w/ objects and the RPL runstream
  - CtrlWord? is the inner RPL compiler dispatcher
  - InTemp? is a routine I've missed in the '48s ROM...
  - ASParse is the assemblers parameter field parser, is written in RPL using
    the seldom seen build-in parser tools (another example for them can be
    found in the BNF parser in the EXAMPLE directory of RPL48)
  - DoDisAss -- one PCO making up the disassembler ! The shortest DA ever
    seen !
  - EC, a cute POL example w/ deep burried surprises
  - 4/5/7 is the system stack display, superseeding the SOL
  - CompEdit$ is responsible for the systems editline
  - I'm not too proud on editLevel1, but might be worth to check out GOTOs
  - Rpl->nLine falls in the same category, but at least it does provide a
    multi-row system stack display
  - IStk is the interactive stack, well know these days but this version
    deals w/ 4, 5 or 7 displayed levels
  - CC, the character set catalog is another POL example and is also
    completetly hooked into the system environment
