Hi; I've inherited a lot of Perl [mostly ActiveState] (and bash) scripts were the former writers and maintainers did not use "use strict" and "use warnings" and have other "less than Best Practices". Most of the scripts are executed on Windows and some of them are executed on a Mac and some are executed on Linux. There is apparently a massive amount of dead code and duplicate code. There are weird dependencies here and there on Cygwin. Apparently there was an earlier (still present?) dependency on MKTools. Some scripts need to be modified prior to first build on a new branch. The builds sometimes work fine and sometimes fail in strange ways.
It would be nice if there was a trace facility built-in to Perl that I could enable that would tell me each line number of each script that was currently executing. I'd love to replace all the Active State Perl code with either Cygwin Perl or Strawberry Perl. Of course I'd like to replace the Windows machines with Linux, but that's not going to happen :-) One of the strange things I see happening is that a path construct of "c:\\dir1\\dir2\\filename" (not quoted in the script is being parsed as "c:\dir1\di2filename" which seems strange. Another situation that seems strange is the use of three backslashes together. I thought that if you had to backslash a backslash it would always come in pairs. What is strange is that this thing works sometimes and then doesn't work sometimes. Now I'm here late at work trying to figure out why the build infrastructure is broken. Thanks, Ken Wolcott -- To unsubscribe, e-mail: beginners-unsubscr...@perl.org For additional commands, e-mail: beginners-h...@perl.org http://learn.perl.org/
