Brian, Thanks for the advice. I can see how that could be misunderstood. In fact, there is also a Scope::Cleanup that does something similar (I discovered in my blog post on blogs.perl.org). Really, this is more along the lines of a "finally" statement than error handling. Take a quick look at the readme file:
https://github.com/jsober/Filter-Cleanup The fault is my own - stackable error handling was a poor - and inaccurate - description. Statements are really there for cleanup of a scope, regardless of whether the code threw an error. I would appreciate it if you would please reconsider. However, if you still disagree, I am happy to rename it, although StackableErrorHandler is probably also misleading, since it implies the code is only called in the event of an error. Do you have any other suggestions for naming it? Jeff Ober On 6/3/12, brian d foy <brian.d....@gmail.com> wrote: > [[ This message was both posted and mailed: see > the "To," "Cc," and "Newsgroups" headers for details. ]] > > In article <201206010249.q512n34q001...@pause.fiz-chemie.de>, "Perl > Authors Upload Server" <upl...@pause.perl.org> wrote: > >> The following module was proposed for inclusion in the Module List: >> >> modid: Filter::Cleanup >> DSLIP: bdppb >> description: Stackable error cleanup like D's scope(exit) >> userid: JEFFOBER (Jeff Ober) > >> >> This module provides a stackable, serial error handler that >> translates into nested eval calls. This makes handling errors much >> simpler and creates much cleaner syntax. > > "Cleanup" as a name didn't suggest any of that to me. > Filter::StackableErrorHandler would though :) > > -- > brian d foy (one of many PAUSE admins), http://pause.perl.org > PAUSE instructions: http://pause.perl.org/pause/query?ACTION=pause_04about > Archives: http://www.xray.mpe.mpg.de/mailing-lists/modules > Please send all messages back to modules@perl.org with no CC to me. > -- Old programmers don't die; they just parse on...
