Re: Understanding CPAN's SCRIPT CATEGORIES

Thank you all for your suggestions.

As to creating a module, at first I thought, "How would this be possible? The only option it has is --help." Then I realized that I could break it into a parser and a code generator. So now I get to rewrite it as a module. Oh joy.

As to its name, the Sub:: modules seems to be about modifying the behaviour of sub's, whereas Devel:: seems to be about creating things. Unfortunately there already is a module Devel::Sub::Which that means I can't name mine simply Devel::Sub without confusion. What do you think of the name Devel::Sub::API?

Comment on Re: Understanding CPAN's SCRIPT CATEGORIES

Replies are listed 'Best First'.
Re^2: Understanding CPAN's SCRIPT CATEGORIES by jethro (Monsignor) on Jul 23, 2009 at 01:09 UTC
API sound so passive and general. How about Devel::Sub::Creator ?	[reply]
Re^3: Understanding CPAN's SCRIPT CATEGORIES by shawnhcorey (Friar) on Jul 23, 2009 at 13:39 UTC
I thought of that. Also, Maker, Generator, and Writer but each of these imply that it would create the entire sub, code included. But it only deals with the interface, so API.	[reply]
Re^4: Understanding CPAN's SCRIPT CATEGORIES by jethro (Monsignor) on Jul 23, 2009 at 14:08 UTC
"API" also implies more than what your module provides. Maybe then just Devel::Sub::Interface or Devel::Sub::Parameter. Or Devel::Sub::Skeleton	[reply]
Re^5: Understanding CPAN's SCRIPT CATEGORIES by shawnhcorey (Friar) on Jul 23, 2009 at 14:38 UTC
Re^6: Understanding CPAN's SCRIPT CATEGORIES by jethro (Monsignor) on Jul 23, 2009 at 15:18 UTC