🚀 go-pugleaf

From: stag!thelake!steve@bungia.mn.org (Steve Yelvington)

I forwarded kbad's note about AC_CLOSE to the Citadel BBS network's C
discussion room, which generated the following from Ian Lepore:

(begin forwarded message)
-----------

   89Jun24 9:37 pm from Ian@The Vale (We have returned!)
  
 YACC == Yet Another Compiler Compiler (not 'C Compiler').  
  
 About that Usenet message from Ken B. concerning AC_CLOSED messages and 
freeing up memory/file handles from within an accessory... I did a little 
playing with the concept recently, and it seems like you get the AC_CLOSED 
message **after** then main application has been Pterm'd by DOS.  This is bad, 
in that the handles in question have *already* been freed as part of Pterm 
processing.  I intend to play with the concept more in the near future, I'll 
post what I find... 
  
  And finally... Someone asked about current versions of libraries for Sozobon 
C.  The most current release of GEMFAST is v1.2, which has TOS 1.4 suport and 
*many* bugfixes over v1.0. 
  
 Speaking of GEMFAST... I'll be releasing v1.3 in the next couple of weeks.  
There is currently one known bug I'll be fixing:  The VDI function 
'vsl_ends()' actually returns 2 integer values (the selected end types), but 
the DRI docs don't mention that.  Thus, the bindings make no provision for the 
return-value pointers, and a call to vsl_ends() results in 2 bombs. 
  
 Speaking of GEM and DRI docs... Here's one for you:  During form_do() 
(dialog) processing, if the user double-clicks on an object defined as 
TOUCHEXIT, the object index of the exit object as returned from form_do() has 
the high bit set.  This sorta makes it into a negative number, and attempts to 
use that return value as an object index in following code results in a 
variety of bombs (depending on the code).  Also, now that this fact is known 
(am I, perhaps, the only one who didn't know this?), I can think of some very 
handy uses for it.  Anyway, if you have a dialog box that has TOUCHEXIT 
objects in it, it is safest to code your dialog call as something like 
"exitobject = 0x7FFF & form_do(tree,0);". 
  
---------
(end forwarded message)


#define steve@thelake.UUCP      pwcs!stag!thelake!steve
#define steve@thelake.citadel   the_land!class68!thelake!steve