Frank Heckenbach wrote:
The African Chief wrote:
Actually, that's almost exactly what my mods do. If IO checking is enabled ( {$I+} ), a proceedure taking no parameters is called that would check the InOutRes state (though I used a different name) and if it's set dumps a dirty message and aborts the program.
For compatibility with BP, you would need to call the variable "InOutRes", and it should be exported, so that programmers can set it manually if they want (this feature of BP might be considered to be a bug by some, but I have found great use for it ...).
I've made use of it, too. Since there's no proper way to raise an I/O error, setting InOutRes seems to next best thing to do.
Therefore, we'll call it InOutRes in GPC as well. Exporting it will be no problem. One little question is its type: should it be Integer as in BP, or Integer(16) (which the BP Integer is in GPC)?
There is no reason why it should not just be "Integer". I can't see why its number of bits should make any difference.
Best regards, The Chief -------- Dr. Abimbola A. Olowofoyeku (The African Chief) Email: laa12@keele.ac.uk Author of: Chief's Installer Pro 4.01 for Win16 and Win32: Winner of PC PLUS Magazine Gold Award (April 1995 U.K. edition) http://ourworld.compuserve.com/homepages/African_Chief/
ftp://ftp.demon.co.uk/pub/ibmpc/win3/apps/chief/pro/chief401.zip