in reply to Re: Log::Dispatch::FileRotate error handling
in thread Log::Dispatch::FileRotate error handling
From my pov the calling module/program should die/croak and the calling program should have the choice to handle the die/croak via eval or to die as well.
Checking disk space/permission etc. involves also the chance to run into a race between check and change of disk space thus an improved error handling would be highly appreciated.