On Thu, Nov 20, 2003 at 05:10:33PM +0800, Autrijus Tang wrote: > On Thu, Nov 20, 2003 at 09:03:40AM +0100, Roderich Schupp wrote: > > > Obviously not a biggy, just a pain for testing (althought > > > the segfault in 5.8.2 is a worry!) > > The segfault went away after rebuilding PAR with Perl 5.8.2 > > (had been built with 5.8.1). > > Right, same thing had also happened here. > > Perl 5.8.2 deliberately broke binary compatibility with 5.8.1 > in order to be compatible with 5.8.0, so "early adopters" will > end up having to recompile XS modules twice. ;-)
5.8.2 has a bugfix for a (perl internal) stack error related to coderefs in @INC. (Which is what PAR is using) Strictly 5.8.2 didn't deliberately or intentionally break anything for non-threaded perl builds. The only deliberate breakage is specifically for calls to some threaded C library calls for threaded perl builds. (Because threaded 5.8.1 unintentionally broke compatibility with 5.8.0 for these calls on threaded perl builds) Upshot - if you're using threads, modules built with 5.8.0 should run with 5.8.2. 5.8.1 might not, so don't risk it. If you're not using threads, modules built with 5.8.0 and 5.8.1 should both run with 5.8.2 no problem. Anything else is a bug. Nicholas Clark
