I've personally noticed that a lot of modules use an Easy subspace to show it's an interface or ability that's stripped down and made simple for you. I think this would be your emphasis. That you haven't written a new framework, but present an easy way to use the existing ones. For example: IO::Pty::Easy which uses IO::Pty.
Maybe a different keyword you would be interested (which seems popular) is *::Simple. For example: CGI::Simple (which uses CGI.pm), SVK::Simple (which uses SVK.pm). This is just how it would seem to me if I were looking for a simple exception handler that makes using exceptions easier. On Sun, Jun 29, 2008 at 1:13 PM, Lutz Gehlen <[EMAIL PROTECTED]> wrote: > > Hi sawyer x, > thanks for your suggestion. > > On Sun, Jun 29, 2008, sawyer x wrote: > > How about Exception::Easy ? > > The idea to put it out of the Exception::Class name space is > definitely worth considering because my module can in fact deal > with any class that implements a throw method and I am planning to > make it still more flexible in a future version. > > However, Exception::Easy sounds too much to me as if it would > implement yet another exception framework which is not the case. I > hope to find something more descriptive of what the module does. > > Thanks for your input, > Lutz
