Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!rphroy!caen!kuhub.cc.ukans.edu!maverick.ksu.ksu.edu!iowasp.physics.uiowa.edu!ns-mx!ccad.uiowa.edu!cadsi
From: cadsi@ccad.uiowa.edu (CADSI)
Newsgroups: comp.windows.ms.programmer
Subject: Re: question regarding catch/throw
Message-ID: <1991Mar30.233601.18981@ccad.uiowa.edu>
Date: 30 Mar 91 23:36:01 GMT
References: <1266500002@cdp>
Organization: CAD-Research, U. of Iowa, Iowa City, Iowa
Lines: 18

From article <1266500002@cdp>, by jeff@cdp.UUCP:
> 
> I recently used Catch/Throw in an application.  If you've used
> setjmp/longjmp before, you should have no problems.

One thing is interesting about these.  They are used via typecast structures
(in this case, arrays).  Thus, when you send a pointer to the thing, the
compiler nags about superfluous & before array.  Geeze, I wish MS would
think about these things.  I like to write warning free code (well as much
as possible).  In order to remove this message, I remove the &.  This
will be real nice if Windows SDK ever decides to implement this stuf as
a structure.

|----------------------------------------------------------------------------|
|Tom Hite					|  The views expressed by me |
|Manager, Product development			|  are mine, not necessarily |
|CADSI (Computer Aided Design Software Inc.	|  the views of CADSI.       |
|----------------------------------------------------------------------------|