Hi, If I grab some Padre time later on today, would removing the reliance on Win32::API appeal?
You only have a few API functions that get called, so wrapping these in an XS module would mean 64 bit Padre on Windows with the next release. I don't see much need for expanded Win32::API usage in the future, and even if there is once the basic XS module is in place, it will be much easier to wrap additional functions. The right thing to do would be help with the Win32::API for 64 bit windows effort - but I lack any assembler skills and I can't get the current version from github to work with VC7 64bit or the version of mingw-w64 I use. I can get it to compile - but I just get access violations on usage. I have an itch that on Citrus Perl, you can do 'cpan -i Padre' as your first post install action everywhere except 64 bit windows. Anyone want to keep Win32::API ? Mark _______________________________________________ Padre-dev mailing list Padre-dev@perlide.org http://mail.perlide.org/mailman/listinfo/padre-dev
