Unix and Linux Discussions Tagged with member_project |
|
Thread / Thread Starter |
Last Post |
Replies |
Views |
Forum |
|
|
|
1 |
9,586 |
What is on Your Mind? |
|
|
|
19 |
19,162 |
What is on Your Mind? |
|
|
|
0 |
40,333 |
OS X (Apple) |
|
|
|
1 |
10,270 |
Programming |
|
|
|
52 |
21,681 |
What is on Your Mind? |
|
|
|
8 |
8,328 |
What is on Your Mind? |
|
|
|
28 |
25,306 |
What is on Your Mind? |
|
|
|
5 |
32,727 |
Linux Benchmarks |
|
|
|
30 |
22,080 |
What is on Your Mind? |
|
|
|
7 |
14,306 |
Programming |
|
|
|
0 |
6,806 |
OS X (Apple) |
|
|
|
5 |
9,237 |
Programming |
|
|
|
8 |
8,774 |
What is on Your Mind? |
|
|
|
5 |
25,478 |
Hardware |
|
|
|
1 |
10,431 |
What is on Your Mind? |
|
|
|
10 |
11,707 |
Programming |
|
|
|
45 |
28,192 |
UNIX for Advanced & Expert Users |
|
|
|
0 |
13,049 |
Programming |
|
|
|
0 |
11,943 |
Programming |
|
|
|
2 |
14,017 |
Infrastructure Monitoring |
|
|
|
6 |
13,463 |
Programming |
|
|
|
6 |
9,797 |
Programming |
|
|
|
8 |
15,459 |
Programming |
|
|
|
0 |
11,387 |
Programming |
|
|
|
13 |
16,455 |
Programming |
|
|
|
7 |
15,661 |
Programming |
|
|
|
2 |
12,023 |
Shell Programming and Scripting |
|
|
|
8 |
25,510 |
OS X (Apple) |
|
|
|
1 |
8,691 |
Programming |
|
|
|
1 |
12,135 |
Shell Programming and Scripting |
|
|
|
10 |
16,279 |
Programming |
|
|
|
6 |
11,850 |
UNIX for Advanced & Expert Users |
|
|
|
1 |
10,326 |
Programming |
|
|
|
0 |
9,885 |
Programming |
|
|
|
8 |
14,972 |
Programming |
|
|
|
10 |
11,845 |
What is on Your Mind? |
|
|
|
6 |
10,021 |
Programming |
|
|
|
9 |
21,504 |
Programming |
|
|
|
0 |
28,442 |
Programming |
|
|
|
6 |
11,419 |
Programming |
App::Cmd::Setup(3pm) User Contributed Perl Documentation App::Cmd::Setup(3pm)
NAME
App::Cmd::Setup - helper for setting up App::Cmd classes
VERSION
version 0.318
OVERVIEW
App::Cmd::Setup is a helper library, used to set up base classes that will be used as part of an App::Cmd program. For the most part you
should refer to the tutorial for how you should use this library.
This class is useful in three scenarios:
when writing your App::Cmd subclass
Instead of writing:
package MyApp;
use base 'App::Cmd';
...you can write:
package MyApp;
use App::Cmd::Setup -app;
The benefits of doing this are mostly minor, and relate to sanity-checking your class. The significant benefit is that this form
allows you to specify plugins, as in:
package MyApp;
use App::Cmd::Setup -app => { plugins => [ 'Prompt' ] };
Plugins are described in App::Cmd::Tutorial and App::Cmd::Plugin.
when writing abstract base classes for commands
That is: when you write a subclass of App::Cmd::Command that is intended for other commands to use as their base class, you should use
App::Cmd::Setup. For example, if you want all the commands in MyApp to inherit from MyApp::Command, you may want to write that package
like this:
package MyApp::Command;
use App::Cmd::Setup -command;
Do not confuse this with the way you will write specific commands:
package MyApp::Command::mycmd;
use MyApp -command;
Again, this form mostly performs some validation and setup behind the scenes for you. You can use "base" if you prefer.
when writing App::Cmd plugins
App::Cmd::Plugin is a mechanism that allows an App::Cmd class to inject code into all its command classes, providing them with utility
routines.
To write a plugin, you must use App::Cmd::Setup. As seen above, you must also use App::Cmd::Setup to set up your App::Cmd subclass if
you wish to consume plugins.
For more information on writing plugins, see App::Cmd::Manual and App::Cmd::Plugin.
AUTHOR
Ricardo Signes <rjbs@cpan.org>
COPYRIGHT AND LICENSE
This software is copyright (c) 2012 by Ricardo Signes.
This is free software; you can redistribute it and/or modify it under the same terms as the Perl 5 programming language system itself.
perl v5.14.2 2012-05-05 App::Cmd::Setup(3pm)