in reply to Re: Rationale for why successive Perl releases are not XS-compatible?
in thread Rationale for why successive Perl releases are not XS-compatible?
chromatic's blog post is a good read, but as he points out, it would actually be beneficial to have an extra layer between perl's internals and user modules to prevent XS code from accessing the internals. I don't disagree with the necessity for changing the internals periodically. It would just be nice to have a binary compatible interface that shields you from those changes...
|
---|
Replies are listed 'Best First'. | |
---|---|
Re^3: Rationale for why successive Perl releases are not XS-compatible?
by Anonymous Monk on Mar 17, 2017 at 17:14 UTC |
In Section
Seekers of Perl Wisdom