Enjoy the incompatible changes section from all Perl history,

https://perldoc.perl.org/perl#History

That's a link to complete changelogs.

Those aren't an "incompatible changes seection".

perldelta covers bugfixes, feature additions etc.

   foreach entry in "https://perldoc.perl.org/perl#History" do
      open entry on browser
      search for "Incompatible Changes" section
      read section contents

Writing a script in Perl to do the above is left as exercise to the reader.

Hint, use LWP.

That's bullshit. I've run exercises from the Orelly CD bookshelf more than a decade old and they just run as is.

Almost all exercises are minimal in nature. They will touch only small areas and (unless the book is based around advanced ideas) will not touch tricky / changing functionality. So I'm not surprised exercises still work.

That just proves the point you got lucky with what language features were used on the exercises.

> That's bullshit.

Dude, there is literally a link with references.

For me, I had been too lazy to use Homebrew or Perlbrew since I don't develop locally per se, but I wanted `Perl::LanguageServer` for use with VS Code – which I'd installed via `local::lib` into `~/perl5/`.

Post-upgrade either various modules weren't found (because they were installed in a versioned path), or they didn't compile because the XS components had been compiled against the prior version of Perl.

Right, that's a risk you take doing local::lib against system perl.

I will often use the system perl to bootstrap https://p3rl.org/Perl::Build which makes building -one- perl for local use easier than perlbrew/etc. - and then https://p3rl.org/App::plx for managing per project environments if I need that

They had to recompile their perl XS bindings, where esp. subversion is horrible to update.