note
kevbot
I have a fairly large code-base that relies on [metamod://Method::Signatures], and I have found that it works very well. However, it depends on [metamod://Devel::Declare]. The documentation for Devel::Declare states,
<code>
WARNING
Warning: Devel::Declare is a giant bag of crack originally implemented by mst with the goal of upsetting the perl core developers so much by its very existence that they implemented proper keyword handling in the core.
As of perl5 version 14, this goal has been achieved, and modules such as Devel::CallParser, Function::Parameters, and Keyword::Simple provide mechanisms to mangle perl syntax that don't require hallucinogenic drugs to interpret the error messages they produce.
</code>
So, for new code I would recommend [metamod://Function::Parameters].
<p>Also, it looks like the author of [metamod://Method::Signatures] ([schwern]) would like for the two modules to work well together. See these github issues,</p>
<ul>
<li>[https://github.com/mauke/Function-Parameters/issues/8|Method::Signatures support]</li>
<li>[https://github.com/evalEmpire/method-signatures/issues/116|Become a wrapper around Function::Parameters]</li>
</ul>
However, these issues are a few years old and I don't know how much progress has been made in addressing them.
1195793
1195800