That would seem like the way to go for XS modules too, as each generation is binary compatible with other versions of the same generation, but not with other generations.As a basic rule, perl 5.x.y will know it's supposed to be binary compatable with 5.x.z, z < y, and will hence include the appropriate directories in @INC, if available at compile time. At least, 5.8.x does so (but I think 5.6.x as well). For instance:
perl -wle '$, = "\n"; print @INC' /home/abigail/Perl /opt/perl/lib/5.8.3/i686-linux-64int-ld /opt/perl/lib/5.8.3 /opt/perl/lib/site_perl/5.8.3/i686-linux-64int-ld /opt/perl/lib/site_perl/5.8.3 /opt/perl/lib/site_perl/5.8.2/i686-linux-64int-ld /opt/perl/lib/site_perl/5.8.2 /opt/perl/lib/site_perl/5.8.1/i686-linux-64int-ld /opt/perl/lib/site_perl/5.8.1 /opt/perl/lib/site_perl/5.8.0 /opt/perl/lib/site_perl .
Abigail
In reply to Re: Modules that differ for different Perl generations
by Abigail-II
in thread Modules that differ for different Perl generations
by bart
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |