JJ> 2: s2p does not run [ well ] on Win98Se. JJ> 3: s2p does not have a help display like a2p. JJ> [ JJ: I have not yet moved to working on the AWK scripts but the Perl code JJ> generated by s2p for even a simple Sed script is more complex than I JJ> expected and I am rethinking the move to Perl from Sed and AWK. ] JJ> 4: s2p (ActiveState win32 port) does not send its output to the Win32 stanbard output. JJ> Work around: I found s2p output in C:\tmp.
This has been bug-reported against 5.6.1. s2p has been rewritten since, and s2p of 5.8.x shouldn't have these flaws. With the rewritten version you have the choice between retaining your sed scripts and translating to a Perl program. You should not expect simplicity in code generated from some non-trivial language. With a little Perl experience you may find that a manual rewrite of all but the most intricate sed scripts is likely to be the preferred solution, particularly if the Perl program will undergo maintenance. The perldoc of the new s2p version contains a detailed discussion of the differences of regular expressions between sed and Perl, which might help. Don't expect too much from a2p. I was once tackling an (admittedly complex) awk program with it, and I gave up soon. It should work well for simple scripts, though. Regards Wolfgang
