Wouldn't distribution become a problem, since Inline::C requires a C compiler? But, that actually made me look for Win32::OLE & indeed it is available for 64-bit version of Perl. I think a better alternative would be create a dll & expose the methods that can be consumed directly via perl. Sounds like this might be a friendlier approach to distributing my code. What do you think? | [reply] |
Inline C produces a dll. That can be packaged and distributed without having to be compiled by every user, but that's not how it is normally done. Though, if the module builds successfully on the AS build servers, then a PPM (binary distribution) becomes available, which satisfies the needs of those who don't have a C compiler.
One of the problems with producing a Win64 package, is that the MS C compiler no longer supports inline assembler. That means moving to using MASM64 to build the interface components, but the Perl build process doesn't support that; and it wouldn't work with non-MSC compiler suites. On top of that, MASM64 is barely functional and barely supported.
Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
"Science is about questioning the status quo. Questioning authority".
In the absence of evidence, opinion is indistinguishable from prejudice.
| [reply] |
Thanks for the explanation. I think I have my answer.
| [reply] |