----- Original Message -----
From: "David Oswald"
Ok, back to work. If you roll back to 0.33_002 do you still have
problems running code that calls cout or uses string?
Not sure - if I revert back to 0.33, Math-Prime-FastSieve-0.33 won't even
compile:
C:\vsnet\Vc7\include\cstdio(16) : error C2039: 'PerlSIO_clearerr' : is not a
mem
ber of 'operator``global namespace'''
I mightn't get much of a chance to look at anything properly until after New
Year ... see how it goes ;-)
And with 0.33_003 the same module throws up those linking errors, which I
guess is what Buk also found.
I think the good news is that not many perl people use MS compilers (even
with ActivePerl), and mingw is fine (even with ActivePerl).
Like I might've said earlier - this is probably fairly easy to solve for
anyone who knows both C++ and MS compilers. (I'm not very inexperienced in
either.)
I am really bothered to think that just adding some #define's and
attempting to use namespaces compatibly has broken something.
Again - the good thing about that being that it's probably fairly
straightforward to solve for anyone who knows C++ and MS compilers.
I suppose I could
install Active State Perl on my Windows system, but I've never
investigated how to get Active Perl co-existing with Strawberry Perl
on the same Windows system.
It's fairly trivial. All the Strawberry stuff is in your path.
When you install ActivePerl you should be prompted as to whether you want
ActivePerl added to your path. Just say "no" ... and make sure that you
install ActivePerl into a location that doesn't have any spaces in it. You
probably also want to refuse the invitation to associate '.pl' with the
ActivePerl interpreter.Then, when you want to use ActivePerl instead of
Strawberry perl just run:
set PATH=C:\perl\bin;%PATH%
(That's assuming the ActivePerl 'perl.exe' is located in C:\perl\bin. Modify
according to where it actually is.)
When you get an MS compiler (which will include nmake.exe, btw), you'll fire
it up by executing (something like) vcvars32.bat - so you could put both
commands into a batch file (named, say 'ap.bat'):
set PATH=C:\perl\bin;%PATH%
vcvars32.bat
Then whenever you want to use ActivePerl/nmake/MSVC++ just execute ap.bat
from the command prompt.
Cheers,
Rob
