Since this is meant to help people who are developing modules
I never actually stated what it was meant for, except for having a function that returns a list of symbols of a certain type in a certain package. It's useable for exporting, but I actually thought of that one after creating the module (I'd not have bothered with a generic function if I only cared about exporting, I would just have made some extention to Exporter).
"Symbol" is not a good top-level name
I think it's a very good name. I think it's logical to group modules by what they do, instead of by who will use it in what kind of script/module.
LWP::Simple is good, Net::HTTP::LWP::Simple would be bad. XML::Parser is good, Data::XML::Parser would be less good. Etcetera. I think the Symbol top level namespace was a good choice, and I'm glad it exists.
Symbol::List would need no description, and many people would use it. Devel::SymbolList would indicate it has something to do with development only (we're not calling Exporter Devel::Exporter just because its sole purpose is to ease module development) which scares off some users. This module is not for power users. Power users have always written their own symbol grabbing code, and will probably continue to do so.
I much prefer Devel::ListSymbols for this module
The module was made to generate a list of symbols, not to list symbols. But that's a very minor issue.
In reply to Re: (tye)Re: Symbol::List
by Juerd
in thread Devel::GetSymbols (fka Symbol::List)
by Juerd
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |