I have a fairly large code-base that relies on Method::Signatures, and I have found that it works very well. However, it depends on Devel::Declare. The documentation for Devel::Declare states,
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 b
+y 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 provi
+de mechanisms to mangle perl syntax that don't require hallucinogenic
+ drugs to interpret the error messages they produce.
So, for new code I would recommend Function::Parameters.
Also, it looks like the author of Method::Signatures (schwern) would like for the two modules to work well together. See these github issues,
However, these issues are a few years old and I don't know how much progress has been made in addressing them.
| [reply] [d/l] |
Another module along this like is Toby Inkster's Kavorka, which seems very powerful.
| [reply] |
kevbot,
Thank you for that info. I have noticed that there is one glitch that occurs in Method::Signatures on occasion. I like to use a func fatal($msg) subroutine in conjunction with caller, to handle fatal errors in some of my programs, and Method::Signatures causes it to sometimes misreport the line from which the error occurred, which schwern alludes to in your link about making it into a wrapper, so it's nice to finally have confirmation of this!
In lieu of this I will try Function::Parameters with the hopes of using it as a replacement. I already like the idea of typing one less char for functions! (fun instead of func)
say
substr+lc crypt(qw $i3 SI$),4,5
| [reply] [d/l] [select] |