1/26    Would like to know if there is a conversion utility for taking a
        very large bourne shell script and turning into a Perl one.  I don't
        look forward to re-writing 20K+ of scripts somebuddy else wrote.  -mtbb
        \_ While this is theoretically possible, the naive version would
           generate nasty code, and even the best version couldn't generate
           good code; the styles differe too greately between sh and perl..
           why do you need to rewrite them in perl?  --dbushong
           \_ because the effort of porting them is less than the effort
              of trying to get sh to do what you want it to do?  -tom
              \_ I would rather deal with sh than with script-produced perl
                 --dbushong
                 \_ Depends on how much it needs to change in the future.
                    Some stuff is a bitch to do in sh.  You can script-port
                    to perl and then rewrite it in pieces over time as
                    required and enhance more easily in the long term this
                    way.
           \_ Becauer PERL r000lez!
        \_ The reason I need to put this into Perl is because Perl is portable
           \_ See if you can license one of the [c]sh programs for NT.  We
              have one at work, MKS Toolkit.  -meyers
           to the NT machines we have as well.  I was hoping there was a
           utility to help out, but seeing as the script needs re-writing
           anyway.....  Perl will also allow us, as Tom-Bud pointed out, the
           ability to code in CGI stuff for better DB-Web application
           integration in future modules.  -mtbb
           \_ bash for NT exists.
                \_ Oh just stop.  None of the ported shells work as expected
                   under NT.  Stop offering half assed unix-centric solutions
                   for NT problems.  Just because it exists doesn't mean it
                   works correctly.
                   \_ bourne shell scripting is NOT UNIX-CENTRIC, it is
                   POSIX.1. Microsloth CLAIMS TO SUPPORT POSIX.1
                   So you don't have to install anything non-microsloth
                   to run the stupid script. Theoretically, just
                   change the path to SH, and run.
                   Don't complain, if you don't at least TRY to run
                   the scripts, as is, under NT.