in reply to Re^2: Installing a missing module - Perl 5.8.3
in thread Installing a missing module - Perl 5.8.3

AIUI, an extension compiled with 5.x.a is guaranteed to work with 5.x.b if and only if a <= b && $Config{archname} has not changed.
So, yes - a build of Time::Piece that was compiled with perl-5.8.3 should be fine with perl-5.8.6.
It's highly unlikely that Windows builds of perl-5.8.3 and perl-5.8.6 would differ in $Config{archname}.

Cheers,
Rob
  • Comment on Re^3: Installing a missing module - Perl 5.8.3

Replies are listed 'Best First'.
Re^4: Installing a missing module - Perl 5.8.3
by ikegami (Patriarch) on Jan 26, 2020 at 15:25 UTC

    Thanks. It's backwards for the OP's needs. It might still work, but it's not guaranteed to work.

    Note that $Config{archname} equality isn't enough. That's why I said "all else being equal".

[reply]
[d/l]
      Note that $Config{archname} equality isn't enough

      UPDATE: I think I've now figured it out - that you were alluding to the possibility of different toolchain involvement, different external dependencies, etc.

      I didn't know that.
      This would also imply that 2 perls with the same version number and same $Config{archname} could be binary-incompatible.
      For over a quarter of a century, PPM installations have relied entirely (and flawlessly) solely upon version number and $Config{archname} to determine which package to install - and now you're telling me that's insufficient.

      Can you please provide an example of a difference that could cause incompatibility, yet not alter $Config{archname} ?

      Cheers,
      Rob
[reply]

In Section Seekers of Perl Wisdom