| 1 |
Hi! |
| 2 |
|
| 3 |
The current code may run on various platforms with various interpreters. |
| 4 |
Try it and enjoy. |
| 5 |
|
| 6 |
Various platforms have been tested. Each has two separate system support files. |
| 7 |
Copy and change a pair of them and check embedded.h for a different system. |
| 8 |
|
| 9 |
You don't have to do much more than starting the compilation process. Check |
| 10 |
the used makefiles in case of troubles. |
| 11 |
That't it. |
| 12 |
|
| 13 |
These are the current system support files: |
| 14 |
|
| 15 |
system | compile with |
| 16 |
---------------------------------------------+--------------------------------- |
| 17 |
Win 32bit using VC on i86/32 compatibles: | nmake -f Makefile.vc |
| 18 |
Linux using GNU C on i86/32 compatibles: | make |
| 19 |
Linux using GNU C on AMD/64 compatibles: | make |
| 20 |
Linux using GNU C on Alpha compatibles: | make |
| 21 |
Mac OS X using GNU C on PPC compatibles: | make |
| 22 |
OS/2 using EMX on i86/32 compatibles: | make -f Makefile.emx |
| 23 |
OS/2 using OpenWatcom on i86/32 compatibles: | wmake -f Makefile.wcc |
| 24 |
SunOS using GNU C on some sparc compatibles: | make |
| 25 |
|
| 26 |
******************************************************************************* |
| 27 |
******************************************************************************* |
| 28 |
******************************************************************************* |
| 29 |
|
| 30 |
This version is a Rexx library version. Therefore the RxFuncDrop won't |
| 31 |
run. Use GciFuncDrop instead; RxFuncDrop will work for builtin GCI support |
| 32 |
only. If you want to migrate it into a REXX interpreters core you have to |
| 33 |
change embedded.h and you have to create a new bridge file. Both can be |
| 34 |
obtained from the current Regina release for an example. You can start |
| 35 |
with embedded.h and gci_rexxbridge.c, of course. |
| 36 |
|
| 37 |
***** |
| 38 |
|
| 39 |
Debugging can be enabled in a script by setting the system environment variable |
| 40 |
"_GCI_DUMP" to some value, e.g. |
| 41 |
set _GCI_DUMP=1 |
| 42 |
or |
| 43 |
export _GCI_DUMP=1 |
| 44 |
|
| 45 |
Debugging must have been enabled while compiling, too. |
| 46 |
|
| 47 |
***** |
| 48 |
|
| 49 |
GCI uses a special technique to allow both calling conventions stdcall and |
| 50 |
cdecl to run with each others name. Don't rely on it in different |
| 51 |
implementations. |
| 52 |
|
| 53 |
***** |
| 54 |
|
| 55 |
The Rexx variable GCI_RC will hold informations about the success of the |
| 56 |
execution of the call. The variable is resetted on each call to RxDefineFunc, |
| 57 |
GciFuncDrop and the called functions. Its format is |
| 58 |
<error code> ": " <description> [ ": " <error location> ] |
| 59 |
|
| 60 |
Using GCI as an external package has the disadvantage of a restricted |
| 61 |
signalling. The single signal that can be thrown is "syntax error". The signal |
| 62 |
may or may not be thrown, always look at the variable GCI_RC. |
| 63 |
|
| 64 |
***** |
| 65 |
|
| 66 |
Have a look at the example Rexx script gci-try.rexx |
| 67 |
|
| 68 |
Cheers, Florian |
| 69 |
[email protected] |