Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!sdd.hp.com!spool.mu.edu!uunet!durer!durer.cme.nist.gov!warsaw
From: warsaw@nlm.nih.gov (Barry A. Warsaw)
Newsgroups: comp.windows.open-look
Subject: Re: XView, C++, and interposition problem (Summary)
Message-ID: <WARSAW.91Mar26124655@warsaw.nlm.nih.gov>
Date: 26 Mar 91 17:46:55 GMT
Article-I.D.: warsaw.WARSAW.91Mar26124655
References: <WARSAW.91Mar22110800@warsaw.nlm.nih.gov>
Sender: news@cme.nist.gov
Reply-To: warsaw@nlm.nih.gov
Organization: Century Computing, Inc.
Lines: 24
In-reply-to: warsaw@nlm.nih.gov's message of 22 Mar 91 16:08:00 GMT


The very simple workaround is to cast your destroy function to type
Notify_func, as in:

static
Notify_value destroyFunc( Notify_client client, Destroy_status status )
{
	...
};


...
Frame frame = xv_create( NULL, FRAME, ..., NULL );
notify_interpose_destroy_func( frame, (Notify_func)destroyFunc );

Makes cfront happy, and since the arguments are still put on the
stack, they get passed correctly to destroyFunc.

Thanks to Sal Cataudella and Daniel Gieskens for their responses.

-Barry

NAME:  Barry A. Warsaw         INET: warsaw@nlm.nih.gov
TELE:  (301) 496-1936          UUCP: uunet!nlm.nih.gov!warsaw