Maybe a way to do this would be to package up a bunch of this stuff as a framework that people could have installed into /Library/Frameworks/ ?
Yes, that sounds good. And then that framework could expose a public, version-neutral API, so that applications that want to embed libperl can link against the framework, and thus be insulated from changes to Perl itself. Maybe it could even come packaged with project templates for building apps that are linked to it.
Perhaps we could give this framework a clever name - something suggestive of the framework that a camel is built around. CamelSkeleton... CamelFrame... CamelBones! Yeah, that's a good name for it.
sherm--
C programmers never die - they're just cast into void.
