"chris elliott" <biol75@york.ac.uk> wrote in message news:3EA8ECBF.9050302@york.ac.uk...
> > Hmm. DMC's extern "C" behavior matches MSVC's. In general, to link with
C
> > functions in C++, you need to use extern "C".
> These functions link fine with VC6; in some cases they were declared as extern but not "C"; in other cases they needed both extern and "C" added

Can you duplicate it with a small example?

I have compiled the wxWindows-2.4.0 lib's and samples and _never_ had to  add any extern "C" to any src file.

Are you aware of the fact dmc still defines __SC__ as well? Because glancig over the current wxWindows cvs checkout, I saw you leave a lot of those intact, where they should have been disabled IMO when compiling with DMC. Further defs.h should have : HAVE_BOOL and HAVE_EXPLICIT, and the private wxString(int) ctor must bij commented out. What commandline options do you use to compile?

I can compile and run the 'minimal example' and most/all of the other sampels without any problem. The only problem I discovered sofar was with the image sample which crashes on JPEG's only.

Again this in 2.4.0. When I some time I will try to compile the cvs checkout.

Arjan

Walter wrote:
> "chris elliott" <biol75@york.ac.uk> wrote in message
> news:3EA8ECBF.9050302@york.ac.uk...
> 
>>>Hmm. DMC's extern "C" behavior matches MSVC's. In general, to link with
> 
> C
> 
>>>functions in C++, you need to use extern "C".
>>
>>These functions link fine with VC6; in some cases they were declared as
>>extern but not "C"; in other cases they needed both extern and "C" added
> 
> 
> Can you duplicate it with a small example?
> 
>