NetNews Usenet Archive 1992 #20/NN_1992_20.iso/spool/comp/os/mswindo/programm/win32/867

Internet Message Format | 1992-09-08 | 1.5 KB

Path: sparky!uunet!sun-barr!ames!data.nas.nasa.gov!taligent!apple!xanadu!ravi
From: [e-mail] (Ravi Pandya)
Newsgroups: comp.os.ms-windows.programmer.win32
Subject: setjmp/longjmp
Message-ID: <[e-mail]>
Date: 8 Sep 92 20:26:06 GMT
Organization: Xanadu Operating Company
Lines: 30

The July NT x86 toolset does not include setjmp/longjmp - the header
file is ifdef'ed out, and it is not in the library. It is a fairly
straightforward piece of assembly code to write, but before I do it,
I'd like to know if there are any subtle reasons why the obvious
approach won't work. Does NT do any odd messing around with stacks,
privilege levels, etc that would make it hard? I have a suspicion that
something like this is the reason it is not in the library.

Unfortunately, our port from UNIX to NT cannot proceed without it, or
some facsimile, since it is used in our own exception handling
package, which is used everywhere. We could move it over to the MS
exception handler, except that it doesn't seem to be available nor
documented yet... Any suggestions?

Furthermore, the compiler insists on treating a function in which some
control paths do not return as an error. Since a lot of our functions
might terminate by raising an exception and doing a longjmp, there are
hundreds of places in our code that provoke this error message. Is
there any way to turn it off, or at least downgrade it into a warning?

Thanks!
    --ravi

    Ravi Pandya
    Xanadu Operating Company
    1891 Landings Drive
    Mountain View CA 94043
    415 903 1316
    415 903 1399 fax
    [e-mail]