🚀 go-pugleaf

In article <2q67fpINNgv5@eccdb1.pms.ford.com> poorman@cc4032.pms.ford.com (Glenn M. Poorman) writes:
>In article <2q65gv$oln@bigblue.oit.unc.edu>, brandon@uncvx2.oit.unc.edu (Brandon Van Every) writes:
>|> Paul Durbin (pauld@verdix.com) wrote:
>|> : I attempt to use a member function as callback but all three arguments (to the
>|> : callback) are garbage. If I make it a friend then the arguments are correct,
>|> : but then I can't get to the class data, without reference thru an instance of
>|> : the class and I don't want the data to be static.
>|> 
>|> : So, what is causing this problem? 
>|> 
>|> Motif is based on C, not C++.  You have to use "extern C" linkage for any of
>|> your callbacks.  You can't register any C++ function directly.  You have to
>|> write a plain C front end for anything you want to have callbacked.
>
>Actually the function does not have to have "extern C" linkage.  It just
>can't be a non-static member function.
>

Actually, the callback function should have "C" linkage.  I have used a 
compiler that passed arguments differently  for C linkage and C++ linkage.
So, if I had a free standing function with C++ linkage and used it as a 
callback function, the parameters would be messed up.  This is not an issue 
with most compilers but be aware it could be.  

Can anyone guess the compiler in question?
--
===============================================================================
Ian Hogg						ianhogg@cs.umn.edu
                                                        (612) 424-6332