> Umm it didnt really answer my original query but I guess since no one > has answered it - either I didnt present it correctly or no one has a > answer to it.
Or you posted it late on Saturday night on a weekend when most US workers have Monday off and may be travelling. Not everyone is on the same schedule as you, so give it a little time. > I probably wont jump into the "I want a newbie mailing list" fray for > this though ;). I don't think it would make a difference. It would be pretty much the same people on either list. There are a couple of people on this list who use ePerl. You might want to repost with "ePerl" in your subject. However, most of us no longer use it. ePerl is getting old at this point and has a pretty small feature set compared to the more actively maintained alternatives. Here's an attempt to answer your questions: > 1. Is die supposed to be handled by ePerl/EmbPerl/Mason > ... or did ePerl end up over ridding something. In that > case I would rather have it restored to the default. First, ePerl has nothing to do with Embperl or Mason. It is a totally separate program. The Apache::ePerl code is very simple, and I suggest you read it at some point. It attempts to eval() your code, and does the behavior you saw if it fails (which is what happens when your script does a die()). I don't think you can change that without changing the code, but that's pretty easy to do. > 2. How do I implement a solution throughout the site without > having to do goofy stuff in every HTML page or module. Solution to what? To having die() trapped? Changing the Apache::ePerl code will be a site-wide change, so I'd suggest you do it there. > 3. Why would anyone do that in the first place ? Why catch exceptions? Usually to allow the program to try something else, clean up resources, or print a useful error message. - Perrin
