----- Original Message ----- From: "Ed Peschko" . . > > well, there are two main issues here > > 1) Has activeperl integrated all of its changes back into the mainline?
I don't understand that question. > 2) with mingw, would modules written in C++ be compatible with the VC++ > ones? > > I'm assuming that #2 won't work correctly because the two c++ compilers would have > have to be ABI compatible, and AFAIK visualc++ uses a proprietary ABI. > > So - how do you go about getting VC++ version 6.0? Only legal way of getting hold of it is to purchase it. There's an el-cheapo version (called "Standard Edition", I think) but it doesn't optimise code. Other than that its quite acceptable. > I'll try camel-pack, but > I'm assuming that this is using mingw, so that issues with #2 would be a problem, > especially with win32-specific issues (ie: using precompiled modules from ppm) > I actually don't think there will be issues with 2). There are a number of C++ modules on cpan - which build fine with either MinGW or MSVC. (Both MinGW and VC++ have both C and C++ compilers, btw.) I *think* there are problems if you try to get MinGW to link to a VC++-built C++ import library (because of name mangling). Are you thinking of trying to do that ? If I'm right about this, it's a problem only with C++ libraries, not C libraries. And the problem doesn't really have any direct bearing on perl that I can see. The ppm issue is not usually ... ummm ... an issue :-) So long as the critical configuration options (such as multi-threading) match, then binaries built with VC++-built perl work fine with MinGW-built perl and vice-versa. Cheers, Rob
