search

Perl-Toolchain-Gang / Module-Metadata

Gather package and POD information from perl module files
http://metacpan.org/release/Module-Metadata/
Other
8 stars 16 forks source link

Moops #16

Closed jddurand closed 9 years ago

jddurand commented 9 years ago

Could it be because package is hardcoded in the module, that it does not find namespace in a Moops based class ?

For instance on my latest MarpaX::Languages::M4 (via dzil):

./..
[MetaProvides::Package] No namespaces detected in file lib/MarpaX/Languages/M4/Impl/Default.pm
./..

If then I'd wish that package could be externalized.

jddurand commented 9 years ago

Please forget, I should use MetaProvides::Class.

shadowcat-mst commented 9 years ago

Came here to say just that. Nice to see you're already ahead of me. Enjoy :D

karenetheridge commented 9 years ago

For third-party syntax extensions like this, it might be reasonable to have a Module::Metadata::Moops (etc) that followed the MMD API but was able to parse this new syntax -- and then things like the dzil plugins can use that without having to write new scanners themselves. It wouldn't be appropriate to put it right in MMD, which is a core perl module.