Hey, what gives? It sounds like you haven't sorted out how standard perl modules work. Why the XS then? That's like running before you're even walking! In normal perl, you'd just store 'Foo::Bar' into @Foo::Bar::Builder::ISA and @Foo::Bar::Store::ISA. In face, just put this snippet into your Builder.pm and Store.pm.
One thing you want to be very careful about is to implement as much as possible in plain perl code. Perl data is often highly magical when viewed from the backend and isn't straightforward at all. Your reasons for writing XS should be to interface with other C stuff that isn't accessible from perl or if a selected function has been found to be too slow by profiling. Generally, anything less conservative than that is gunning for trouble.
package Foo::Bar::Builder; # Same for ::Store use vars qw( @ISA ); @ISA = 'Foo::Bar'; 1
In reply to Re: XS Modules: Dependencies
by diotalevi
in thread XS Modules: Dependencies
by esskar
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |