Tk on ActiveState runs pretty much the same as on linux. There are a few bugs, most noticed is that on win32 , select only works on socket filehandles, but not on pipes, so IPC is a pain in the A** unless you use sockets or shared mem for the IPC. There are work arounds, just groups.google for them. ActiveState, (I'm just going on memory here), uses Microsoft's latest Visual C, to build itself, and it's modules. So the problem comes in that if you try to use a precompiled ppm that wasn't made with the exact same compiler and settings, it won't work.
The Cygwin build tries to use gcc, but then your binaries are incompatible with ActiveState. The aforementioned Strawberry and Vanilla Perl, tries to fix this, by make a standardized setup. I totally avoid win32, so I may be off slightly in my observations, but other monks can straighten you out. So Tk on win32, does use the win32 subsystem, the problem is in how you compile them..... either with Microsoft tools, or opensource tools.....it's all too complicated and expensive to deal with, considering Perl and Tk compile and run perfectly for free on linux.why does your code execute fine when activestate executes it, but not when cygwin's perl executes it It sounds like your Cygwin installation is broken. It is pretty hard to get it setup right, so most people don't bother with it. Is there a Cygwin maillist you can ask this on?
| [reply] |