| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | Rexx`ercising |
Hello All!
I posted a message a couple days ago about problems with my Rexx Exit
Handler, specifically RXSIO (intercepting say, trace, and error output).
I kept getting a sys3175, usually in REXX.DLL, sometimes DOSCALL1.DLL and
Borland's C215MT.DLL.
Well, I found the problem! All I had to do was declare my exit handler as
LONG APIENTRY (__syscall) and the problems cleared up! It only took me 3
days to find this!!!! arrrrggghhhhh! :-) I had only declared it as LONG
before. Adding the APIENTRY fixed everything (so far)!
btw, I saw someone that posted about trying to create External Rexx
Functions with Borland C++ for OS/2. Here's something I've noticed, you
cannot use the macro from rexxsaa.h for prototyping,
RexxFunctionHandler myfunc;
You must prototype/declare your external routines like this.
For example,
won't work:
RexxFunctionHandler myfunc;
will work
ULONG APIENTRY myfunc (PUCHAR, ULONG, PRXSTRING, PSZ, PRXSTRING);
For some reason RexxFunctionHandler doesn't work, at least in my experince.
Also, I declare my external Rexx functions as ULONG APIENTRY.
Phil
Fido: 1:124/8014.1 | Internet: phil.crown{at}bluecafe.com
--- Blue Wave/Max v2.22c Beta
* Origin: * MacSavvy OS/2 BBS * Dallas, Texas * 214-250-4479 * (1:124/1208)SEEN-BY: 50/99 270/101 620/243 711/401 409 410 413 430 808 809 934 955 SEEN-BY: 712/407 515 517 628 713/888 800/1 7877/2809 @PATH: 124/1208 1 396/1 270/101 712/515 711/808 809 934 |
|
| SOURCE: echomail via fidonet.ozzmosis.com | |
Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.