Hello Paul!

I was searching through some saved messaged looking for the number to
subscribe to DevCon :-) and found this.

ac> I use Borland C++ for OS/2 1.0.  I haven't come across any bugs, but then
ac> I haven't pushed it very far.  Are there any bugs I should be aware of?

PE> From the top of my head,
PE>
PE> 1. setvbuf with values greater than 64k fail.
PE>
PE> 2. The example program in the Borland book on how to use signal()
PE> doesn't compile, and obviously when you're trying to use it in
PE> real life (e.g. trying to recompile zip/unzip I think it was), it
PE> fails.

The below example from BCOS2 v2.0, as you posted, it does not compile, but I
made two changes below and it compiles... and.. works! :-)

/* This example installs a signal handler routine to be run when Ctrl-Break
   is pressed. */

#include 
#include 
#include 

void catcher(void)
{
   printf("\nNow in break routine\n");
   exit(1);
}

int main(void) {
  //signal(SIGFPE, (void (cdecl *) (int)) catcher); // won't compile
  signal(SIGINT, catcher);                          // will compile, SIGINT
    for (;;)
      printf("\nIn main() program\n");
}

Weird, huh? :-)

phil.crown{at}bluecafe.com


--- Blue Wave/Max v2.22a