Re: Plugins: any advice or docs?

in reply to Plugins: any advice or docs?

I would start with Plugin::Tiny and also take an elevated view of known plugin systems like DBI and Template (Template::Plugin). I myself would like to incorporate such a plugin system and replace my "preset" modules inside Spreadsheet::HTML. This would allow others to publish their own CPAN modules without needing to submit patches/pull requests to me. This is what i feel a plugin system is for: allowing external code to be attached to your own, to flow through your code (be it an engine or framework) without changing that codebase.

jeffa

L-LL-L--L-LL-L--L-LL-L--
-R--R-RR-R--R-RR-R--R-RR
B--B--B--B--B--B--B--B--
H---H---H---H---H---H---
(the triplet paradiddle with high-hat)

Comment on Re: Plugins: any advice or docs?

Replies are listed 'Best First'.
Re^2: Plugins: any advice or docs? by Anonymous Monk on Jan 15, 2016 at 01:17 UTC
Why Plugin::Tiny over a core module like Module::Pluggable?	[reply]
Re^3: Plugins: any advice or docs? by Anonymous Monk on Jan 15, 2016 at 18:31 UTC
You must have missed that the OP already listed that module. Why repeat what they already knew? Offer new information, not rhetrolical questions.	[reply]
Re^4: Plugins: any advice or docs? by davies (Prior) on Jan 15, 2016 at 18:39 UTC
I did NOT know that it was a core module. I did not think the other anonymonk's question was rhetorical, either. I'd like to know the pros and cons of any relevant module, core or not. Regards, John Davies	[reply]

In Section Seekers of Perl Wisdom