Mercurial > hg > Members > kono > nitros9-code
view lib/alib/alib.intro @ 2772:0a3f4d8ea6d5
Found ENDC in wrong location in dwread.asm and dwwrite.asm. Corrected.
Moved the native 6309 code in dwread.asm and dwwrite.asm into the H6309 labeled area and changed IFEQ H6309 to IFNE H6309. Also moved the 57600bps 6809 code to the default location. This change had been done in the old dwread.asm and dwwrite.asm files to make it easier to follow. Though these two files were overwritten from the HDBDOS project dwread.asm and dwwrite.asm files. So this conversion needed to be done again so it made the source easier to follow.
author | drencor-xeen |
---|---|
date | Wed, 23 Jan 2013 12:36:55 -0600 |
parents | 7d70b7e1cb21 |
children |
line wrap: on
line source
RMA Library by Bob van der Poel WARNING: The entire contents of this file including the documentation and the actual binary library code are protected by copyright and is the sole property of Bob van der Poel. You are given permission to use this software and to post it on other information systems, etc. However, you may not sell it, or claim it as your own. Any commercial expoltation will be prosectuted to the full extent of the law. Bob van der Poel Software P.O. Box 57 P.O. Box 355 Wynndel, B.C. Porthill, ID Canada V0B 2N0 USA 83853 To use the routines in this library, just include calls to them in your programs with a "lbsr". For example, the following code segment calls a library routine to print a number via standard out: ldd number lbsr PRINT_DEC To use a routine make sure you have set up all the registers properly. None of the routines use any memory other than stated. Since the hardware stack is used for all temporary variables all the routines are re-entrant and shareable. It is up to the user to ensure an adequate stack area. Note that most of the routines have all uppercase names. It is hoped that this will make your code more readable since you can tell at a glance which routines are external. To compile an assembler program using the library first use RMA to generate a ".r" file, then use RLINK to compile. A sample command line would be: rlink yourprog.a -o=yourprog -l=/d0/lib/alib.l The file alib.doc is a formatted listing of all the commands available in the library. Just list it to your printer. Included in the SRC directory is the file "makefile" which can be used with MAKE to create a new library file. List "makefile" first to see which directories, etc. you'll need. Also included on the disk is the file "LIB/alib.l". This is the complied version of the library, ready for you to link with. If you have any comments or suggestions for future improvement--or even if you want to send money (yes, I take contributions!)--please write me at the above address or email bvdp@uniserve.com.