| [reply] |
| [reply] |
Because Maypole has lots of problems that need to be fixed, like:
- abysmal error handling and recovery (mostly inherited from UNIVERSAL::require)
- Bad documentation
- Bad extensibility as soon as more than one object is involved in one action
- Bad logging infrastructure, ranging from nonexisting logging to wildly spewed warnings that can't be disabled
- ...
Many of these things are being worked on, by sri and others, but I wouldn't use Maypole in a setting where there is a client that pays for a working project that goes beyond beerdb in complexity.
| [reply] |
abysmal error handling and recovery (mostly inherited from UNIVERSAL::require)
I don't get what you mean with "inherited from UNIVERSAL::require", but error and recovery is nice with the new exception handling.
Bad documentation
There are still some small holes but it got a lot better since we are using Test::POD::Coverage. ;)
Bad extensibility as soon as more than one object is involved in one action
TIMTOWTDI, I tend to like Maypole::Component for complex stuff.
Bad logging infrastructure, ranging from nonexisting logging to wildly spewed warnings that can't be disabled
Dunno what you mean with "wildly spewed warnings that can'be disabled", you have to overload debug() to enable debug information.
sub debug { 1 }
What would you expect from a "good" logging infrastructure?
I already invited you to our mailing list, it would be much more productive to post your complaints there. ;) | [reply]
[d/l] |
