Andy Armstrong has set up a TAPx::Parser subversion repository on one of his servers and he and I are now collaborating to get it working on Windows. Andy's already fixed one Windows bug and I've committed code to make colored test output the default unless running on Windows or not running in a terminal.
Andy's going to look into providing anonymous read-only access so that people can play with 'bleed' rather than me hastily uploading a new development version every few days.
Not only does this mean that someone familiar with Windows can look at the Windows issues, but it also means that I won't have to buy a Windows laptop (though I might do it anyway. Someone's contacted me about an inexpensive on).
Re:Excellent work guys
Ovid on 2007-01-18T07:30:02
That would certainly be a nice bonus for Windows users. Are you sure that $^O sometimes returns MSWin32? I thought it was always Win32. If this is documented somewhere, I'd love to read that.
Re:Excellent work guys
link on 2007-01-18T11:36:48
I'm not really sure. Tbh I just copied and pasted it from else where (Perl.pm and Source.pm)
My activestate perl does.
G:\Documents and Settings\link>perl -e"print $^O . \"\n\";"
MSWin32
As for docs , perldoc perlvar says
In Windows platforms, $^O is not very helpful: since it is always MSWin32 , it doesn't tell the difference between 95/98/ME/NT/2000/XP/CE/.NET. Use Win32::GetOSName() or Win32::GetOSVersion() (see Win32 and perlport) to distinguish between the variants.Re:Excellent work guys
Ovid on 2007-01-18T11:48:23
Thanks. By the way, your one-liner can be simplified with the 'l' (el) switch which forces a newline after every print:
perl -le "print $^O"That's very handy when I'm writing quick utilities.