It's pretty unsatisfactory when you purport to have a GUI OS, but have to drop into a crippled DOS command shell window with no way to scroll up and down to run your scripts. To be fair, Windows Perl development gets a little better if you're using a decent editor like UltraEdit. Still, I develop on Unix and Mac, and just transfer stuff over to Windows. I also got into the habit of using many more log files for scripts that run on Windows, and printing practically nothing to stdout. I've not used Package Manager, and have too much respect for myself to want to try. It seems to be more involved than anything on Mac. So I restrict myself to simple modules on Windows. I found that certain legal Perl constructs (I seem to remember that my() inside control structures, such as in for, didn't please ActiveState) don't work with at least one major Windows Perl implementation. So I have to rewrite some legal scripts to get them to run on Windows. So based on personal experience, yes, the Windows Perls are rough around the edges. Useable, though. I'd guess that everyone who monitors c.l.perl.misc has noticed the upwards creep of Windows Perl related posts - they seem to be more technical-support oriented than for the other platforms (as opposed to language-related). As I mentioned once before, I'd like to see Windows Perl get better. Windows is going to be around, and personally I'd like to see VB and everything like it obliterated. :-) But first and foremost, I boost Unix (Linux) and MacOS. :-) On Wed, 2 Dec 1998, Rich Morin wrote: > Interesting, but not all that surprising. MacPerl has been around for > several years and is a mature implementation. Windoze Perls are still > in pretty poor shape (or so I'm told :-). Also, M$ works hard to get > folks to use VB, etc. All Apple has to offer is AppleScrap, which is > not a reasonable alternative to MacPerl for many applications... ***** Want to unsubscribe from this list? ***** Send mail with body "unsubscribe" to mac-perl-request@iis.ee.ethz.ch