in reply to Padre and Strawberry Perl problems

I will try to switching to Strawberry Perl 32bit as I read that compiler doesn't have these issues?

No.

A failing test is generally not a compiler issue, so 32bit or 64bit, makes no difference.

Look at the matrix, look at the win32 reports, version format error, unexpected warning ... these are not 32/64 bit compiler issues, the module got compiled successfully, it just failed a few tests

Other than that is it possible to install Padre first and then update the Strawberry Perl?

No.

But, as long as you it using a portable perl, and you don't overwrite that perl with a new perl, then you'll have two perls installed, and in that way you can install padre and then upgrade your perl, and padre will still work

Replies are listed 'Best First'.
Re^2: Padre and Strawberry Perl problems
by Anonymous Monk on Jan 14, 2016 at 11:15 UTC
      sorry but how do i patch? yea i also figured DWIM Perl is rather outdated so I wanted to use newest strawberry perl and update to newest Padre.
Re^2: Padre and Strawberry Perl problems
by girarde (Hermit) on Jan 16, 2016 at 22:25 UTC
    Piling on I will note that strawberry-perl-5.22.1.2-64bit will not allow Padre to install, and neither will the 14 January snapshot of OpenBSD. The former fails as described above, and the latter says it wants a perl compiled with threads. The real absurdity is that I only wanted Padre because I read it has a vi mode, and I want a vi for Win 7. Not vim, really; I want good old nvi.
Re^2: Padre and Strawberry Perl problems
by diyaz (Beadle) on Jan 14, 2016 at 17:17 UTC
    i installed the 32bit strawberry and the Wx module will install properly but the Debug::Client still fails.

      i installed the 32bit strawberry and the Wx module will install properly but the Debug::Client still fails.

      How ? How did it "not work"?