Hello, Brian,
great to hear that! Numerous things were already expressed, so I simply
encourage you to accept this proposal.
>3) The Inline ILSM API will need to be set in stone. The release of
>Inline/Inline::C will be more closely bound to the release of Perl. Bug
>fix releases can still be made but they will need to be 100% backwards
>compatible. Any changes to the ILSMs must always continue to work with
>the core Inline as well as the CPAN Inline. Major changes in the
>interaction between Inline and an ILSM will need to wait for a new Perl
>release.
I think this is a very common problem, not specific to core
integration.
As soon as the ILSM API changes another way than by "simple" extension,
*all* ILSM's might need to be adapted because users might want to
intermix various Inline modules, either in their perl installation or
even in the same script. Currently there are already a few Inline
modules, but their number will grow as well as the number of developers
and maintainers. As these numbers grow, interface synchronization will
become more difficult.
I'm not sure how to solve this. Maybe there could be a fix meta
interface, enabling a certain ILSM to request an interface according to
spec. 5.3 and another ILSM to work according to spec. 7.4
simultaniously.
>This is the perfect chance to
>see Inline start replacing XS as the standard way to extend Perl.
So think I and suggest to take it.
Greetings
Jochen
