> Is it a bug or a requirement? In either case, it probably needs fixing > rather than FAQ'ing. >
I guess it's a bug, and you're right it should be fixed. But until that can be done it should at least be documented. It's a pain to have your progress halted by something so trivial. >IIRC, Inline::CPP creates the package one level below the current >package. Not sure if this is a bug or by-design. >I think if you dig (in the build directory), you'll find that your >package comes out as ChmFile::ChmFile. I haven't been working with it >for a while, but I think Inline::CPP may need some kind of option to >control this behavior. That's right, that's exactly what happens. But how am I supposed to build it then? If I don't put a package statement it comes out as main::ChFile and I can't use the VERSION and NAME configurations. It's weird though, it works quite fine if I use it without those (as in, just copy the ChmFile.pm to one of the lib directories), but it's obviously a bad solution since every time you run a script that uses the module it has to be compiled and creates the _Inline cache. Has anyone ever build something like this for the CPAN? And if so, how? Alex
