It's concerning that people have been infected with the so-called "Perlish Coding Style" (perl.4pro.net/pcs.html.)
The top level namespace was probably a bad move.
I can't see a use for this at all.
5 out of 8 found this review helpful. Was this review helpful to you? Yes No
I disagree with David Cantrell's harsh review. The code is OK, although stylized in a uncommon way. There are some tests.
The Synopsis shows how this can be used as part of a simple internationalization system.
The project could definitely use more documentation to explain what it's particularly great it, but I found it decent and novel.
5 out of 6 found this review helpful. Was this review helpful to you? Yes No
Unnecesary, and the code is utter shit.
4 out of 9 found this review helpful. Was this review helpful to you? Yes No
This is a trivial OO wrapper implementing the concept called a dispatch table (ie. subrefs in a hash). All of its methods are direct equivalents to a single statement manipulation of a hash, so it hides the intent of trivial code behind an API. You donâ€™t get any added simplicity for that obscurity, but you do get an extra dependency.
The module name is horribly chosen: I certainly wouldnâ€™t think to use â€œchestâ€ as a keyword when searching CPAN for something like this â€“ assuming I ever felt the need for an OO dispatch table in the first place. It also opens a new top-level namespaceâ€¦ why it needed to, Iâ€™m not sure.
At least it has decent docs and a superficial few actual tests.
To make an unnecessarily long story short: stay away.
8 out of 9 found this review helpful. Was this review helpful to you? Yes No