Re: Turning a script into a module

[barbie]

Rather than thinking about warn and die when something goes wrong, think about return codes.

If something goes horribly wrong, I usually return undef, then the caller can check whether anything was returned and handle it as it wishes. In some cases I also setup an internal error code and/or error message (ERRNO, ERRMESS), which can be accessed like Package::ERRNO. This then puts the reliance on the caller to handle the errors as they see fit.

Regards having a PrintHandler, passing that as you have seems fine, but if this is just for warnings and errors, I would personally use the return codes. Then again if this is for own use then it probably isn't an issue, if it was for CPAN you might want to consider that others might not want to print anything at all.

--
Barbie | Birmingham Perl Mongers | http://birmingham.pm.org/

[eyepopslikeamosquito]

If you want to see nothing at all, you can use:

PrintHandler => sub {}

Many of the methods are very long-running, so most users want feedback about their status (and that the machine has not hung). A PrintHandler callback function is the best I have thought of so far. I suppose a GUI front-end could display the status message in a window.