Jan,

I understand your concern about V2008.  I've had to install the msvcrt
redistributable for some of my projects built under VS2005/8.

As for 32/64 compatiblity, the ppm library has separate versions for 64
and 32 bit perl already, I believe.  If that is the case, conditional
complilation (#ifdef __AMD64) should be able to handle the 64 and 32 bit
versions.  The current code for 32 bit will be able to remain.

Steve

-----Original Message-----
From: Jan Dubois [mailto:j...@activestate.com] 
Sent: Monday, February 16, 2009 5:11 PM
To: 'Cosimo Streppone'; Bauer, Steven
Cc: libwin32@perl.org
Subject: RE: Win32::API port to 64 bits

On Sat, 14 Feb 2009, Cosimo Streppone wrote:
> In data 13 febbraio 2009 alle ore 22:00:01, Bauer, Steven
> <steven.ba...@amd.com> ha scritto:

> > with either VS2008 or VS2005 or just the SDK and get it available on
> > the public net. Which do you prefer?
>
> Don't know. I guess we should aim for VS2008, since it's the most
> recent version anyway.

Personally I would like it if Win32::API could be compiled with the
Windows
2003 SP1 SDK compiler because that way it would not have additional
dependencies on other runtime libraries when compiled this way (which
makes it easier to bundle the module with PAR/PerlApp/Perl2Exe).

I suspect though that if it compiles with 2008 that it will also compile
with 2005.  I haven't looked into it though; maybe the support for
intrinsics
in 2008 is much improved compared to 2005.

It is also not clear to me how the changes for 64-bit will affect the
32-bit
version.  Again, I would prefer that the 32-bit code remains compatible
with VC6 so it can link against MSVCRT.dll.  This would argue against
using
intrinsics for the 32-bit code branch, even if you used them for the
64-bit
code.

In the end the people writing the code will have to make the decision,
but from my point of view the best solution would be to separate out
the assembly code into separate source files and compile them using
MASM/ML64
instead of relying on the compiler specific intrinsic functions.

Cheers,
-Jan



Reply via email to