Using reqtools.library

   If you are a C programmer all you need to do is include the correct header ('libraries/reqtool.h') and open

reqtools.library. After that you can use the functions in the library as if they were C functions. If your program quits it must of course close the library again. See 'demo.c' for an example.

   Glue code for several compilers/languages is included with ReqTools 2.4. Look in the Glue directory of the

ReqTools distribution to see if glue code exists for your compiler and/or programming language. If it doesn't and you write your own please send it to me and I'll include it in the next release of ReqTools.

   Note that the source for the Manx C libraries is the same as for the SAS/C libraries.  See the README.Manx file

in the archive 'Glue/Sas-C/LibSource.lha'.

   Manx C users may have to edit '.html>libraries/reqtools.h' and change the library (GfxBase, IntuitionBase, etc.) fields

to rt_GfxBase, rt_IntuitionBase etc. Seems there is a bug in some versions of the Manx C compiler that has problems otherwise. Let's hope this gets fixed soon :-)

   Functions allowing a variable number of arguments can't be called using pragmas (in-line library calls, no glue

code required). So if you use these you must always link with LIB:reqtools.lib or LIB:reqtoolsnb.lib (for SAS-C, or with the specific libraries for your compiler/language).

   Assembly programmers should also include the correct files and open reqtools.library.  To call a function they

must load A6 with the library base, put the arguments in the appropriate registers and jump to the library vector offset of the function they want to call.

   Remember to open the library with a specific version number if you wish to use features only found in that

version (for example: screen mode requester).

All library functions are explained in the autodoc file 'reqtools.doc'.

Enjoy.

Contents page

Index

Using reqtools.library