On Thursday 01 December 2011 00:38:11 David Oswald wrote: > At first blush it seemed that was going to be the main problem. But > then I've run into another one that, while various solutions seem > evident, I'm not sure quite what way to go. Here is a representative > example of the relevant output from one of the CPAN smoke testers: > > -------------------------- > > Output from '/usr/bin/make test': > > Error. You have specified 'C++' as an Inline programming language. > > I currently only know about the following languages: > AS, ASM, C, Foo, GASP, NASM, as, asm, foo, gasp, nasm
I've seen this problem many times as well in the Inline::Python smoke test
reports. It's a real hassle and I think even the largest installation problem
for Inline::Python. A solution would be greatly appreciated.
Reading the Inline docs, the config file is in fact just a cache of the Inline
languages' meta data. The question is: is it even worth it? When using Inline,
I tell it already, which language I want to use. Inline has to load the module
anyway so all that's saved here is the call to register, which for
Inline::Python is just:
sub register {
return {
language => 'Python',
aliases => ['py', 'python', 'PYTHON'],
type => 'interpreted',
suffix => 'pydat',
};
}
Reading in a separate file can't possibly be faster or even anywhere as fast
as executing a constant sub that's already loaded. Considering that the
performance advantages are rather dubious and the config file is a big source
of problems I really wonder if simply removing this caching mechanism might
not be the best option?
Regards,
Stefan
signature.asc
Description: This is a digitally signed message part.
