in reply to Re^2: Interactive perl on windows
in thread Interactive perl on windows

The psh package does not work

Please explain does not work for us who do not sit right beside you. What do you expect, what happens instead? Post any error messages you see.

Alexander

--
Today I will gladly share my knowledge and experience, for there are no sweeter words than "I told you so". ;-)

Replies are listed 'Best First'.
Re^4: Interactive perl on windows
by horsegoalie (Initiate) on Mar 30, 2011 at 15:47 UTC
    So, the issues with psh boiled down to a few things, which with some expert help here we were able to solve... 1) nmake is not available on Windows 7. We need to use dmake, so, the standard build process fails with psh. 2) On line 267 of Psh.pm, there is a line that states: @Psh::last_result= @result= @$result; This line does not work in the latest builds of Strawberry or Activestate. Setting the line as follows works: @Psh::last_result= @result; Now that we have a build of psh that works, we are pretty happy...
Re^4: Interactive perl on windows
by horsegoalie (Initiate) on Mar 31, 2011 at 13:28 UTC
    We found the issues in the psh.pm and fixed them. The first issue on windows 7 is that you need to use dmake, not nmake. We changed the makeFile and were able to compile. The second issue was an error in the code itself, at least with the latest Activestate and Strawberry. It is on line 267 of Psh.pm. A line with two equalities on it throws errors.
      The first issue on windows 7 is that you need to use dmake, not nmake

      The operating system is not the controlling factor, the perl -V:make entry is, which you can override with perl Makefile.PL MAKE=nmake or perl Makefile.PL MAKE=dmake ...

        You are right, and my lack of experience is showing through here. The rest of the cpan/activestate packages we use compile fine without needing to change the compiler flag. For an inexperienced user, the psh install was not nearly as transparent as tksh, tk, or many other packages.