Front page | perl.module-authors |
Postings from December 2011
Please define "not acceptable"... as according to this, http://mingw-w64.sourceforge.net/, project page, it is acceptable for Perl (5.12.0 and later) as well as the Strawberry Perl Project. So who is it not acceptable for? ;-) FWIW... having tried strawberry, I wasn't impressed upon trying to install my first cpan module. major failure(s) due to Windows environment.. -- THOUGH....,part or all of that could be because I use Bash for my windows 'Shell', which currently is only running w/a Cygwin version (interestingly, the NT calls under Win32, will usually take '/' as easily as '\'... Yeah... I mix and match environments a 'lot'. I like them all to play nice together, but wanting so maybe I have a larger than average interest in cross platform compatibility -- but .. um... 8 years ago , was the loaner using UTF-8, complaining about all the incompat progs...,.. (linux was the first to provide support). Windows is still 'iffy'...depending on program. (Native Vim on Windows...can't use UTF-8 encoded files (except in limited cases), but the Vim/Gvim on Linux displaying on Windows (X) can. So can Windows based TTY programs (SecCRT). Compat, reliability and support problems are not limited to CPAN, by any means... But not being bound by corporate greed, it could be come an example of best practices...rather than being somewhere in the middle of the pack...CP Dana Hudes wrote: > Actually while a port of gcc is available of Windows, that is not acceptable for native Windows Perl. That has to be compiled by the MS compiler Visual Studio C/C++. So too for Solaris: Even the OpenCSW project builds Perl for Solaris with the native compiler Solaris Studio. The cygwin Perl is built with gcc. > > BTW Solaris Studio is available for Linux. > Dana Hudes >Thread Previous | Thread Next