home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Shareware BBS: 18 REXX
/
18-REXX.zip
/
vxtech07.zip
/
README.TXT
Wrap
Text File
|
1994-08-05
|
3KB
|
78 lines
============================================================================
VX-REXX Tech Note #7:
Designing REXX-aware Applications
August 1, 1994
This tech note is NOT specific to VX-REXX. You need a C
compiler to compile the source examples.
----------------------------------------------------------------------------
Eric Giguere
Watcom International
============================================================================
Abstract
--------
This is the source that accompanies the article "Designing REXX-Aware
Applications", in the REXX Report, published by the publishers of
OS/2 Developer and available on newsstands or directly from Miller Freeman.
The article text is not repeated here. The article discusses in
general terms what it means to make a "REXX-aware" application. The source
code presented here shows you how to do it.
Each set of source code is presented in its own subdirectory. You should
look at them in a certain order, as they build on each other:
RUNMACRO -- Shows how to call the RexxStart() function to run a
macro.
FUNCS -- Shows how to write a simple external function.
SUBCOM -- Shows how to write a simple subcommand handler.
EXITS -- Shows how to use system exits to intercept interesting
events.
INLINE -- Shows how to run inline (in memory) REXX code.
VARPOOL -- Shows to to access the REXX variable pool.
Each subdirectory includes makefiles for use with WATCOM C/C++ 9.5 or up
and CSet++ 2.1. To make for WATCOM C/C++, use the command:
wmake /f makefile.wat
For CSet++, use:
nmake /f makefile.ibm
Eric Giguere
Watcom International
giguere@watcom.on.ca
Disclaimer:
-----------
The source code in this package is Copyright 1994 by Watcom International,
a PowerSoft company, and is presented as-is with no explicit or implied
warranties. Permission is granted to distribute this package and to use
the source code in your own programs. If you do use the source code, there
is no requirement to label your programs or to otherwise acknowledge the
use of the code.
Eric would, however, appreciate it if you told him you found the code
useful and that if applicable you tested it with VX-REXX.