Setting up helper objects in App::Cmd

McA has asked for the wisdom of the Perl Monks concerning the following question:

Hi all!

Another question to App::Cmd:

Where is the right place to set up helper objects that are accessible to all commands like loggers or database handles?

Best regards
McA

Comment on Setting up helper objects in App::Cmd Download Code

Replies are listed 'Best First'.
Re: Setting up helper objects in App::Cmd by tobyink (Canon) on Sep 25, 2012 at 10:21 UTC
I'd generally name my modules things like: MyApp::Command::Foo MyApp::Command::Bar MyApp::Lib::Foobar MyApp::Lib::Database And instead of loading library modules at compile time with `use MyApp::Lib::Database`, defer loading to run-time (with `require MyApp::Lib::Database`) inside your command's `execute` method. This means that you can avoid loading up database connections, etc when the user is just running, say, `myapp help`. Load them only once they're needed. PS: a release using this technique is P5U. `perl -E'sub Monkey::do{say$_,for@_,do{($monkey=[caller(0)]->[3])=~s{::}{ }and$monkey}}"Monkey say"->Monkey::do'`	[reply] [d/l] [select]
Re^2: Setting up helper objects in App::Cmd by McA (Priest) on Sep 25, 2012 at 11:22 UTC
Hi Tobyink! Once again thank you for your reply. A ++ for that. When I need to do some module initialization for EVERY command. Is there a place/method to do so? Especially when I do initialization work based on the global options. I don't like the idea of doing the same thing, like `require SomeLib; SomeLib->init();` [download] in every command's execute method. Best regards McA	[reply] [d/l]