view release on metacpan or  search on metacpan

inc/Module/Install.pm  view on Meta::CPAN

use 5.006;
use strict 'vars';
use Cwd        ();
use File::Find ();
use File::Path ();

use vars qw{$VERSION $MAIN};
BEGIN {
	# All Module::Install core packages now require synchronised versions.
	# This will be used to ensure we don't accidentally load old or
	# different versions of modules.
	# This is not enforced yet, but will be some time in the next few
	# releases once we can make sure it won't clash with custom
	# Module::Install extensions.
	$VERSION = '1.16';

	# Storage for the pseudo-singleton
	$MAIN    = undef;

	*inc::Module::Install::VERSION = *VERSION;

lib/App/Framework/GetStarted.pod  view on Meta::CPAN

Then the database option would be set to 'listings2_db' if no options were specified by the user at the command line.

By default, the application is called with the options HASH as the 2nd parameter. Using the option values is discussed 
in L<Application body>


=head3 Arguments

The command line arguments specification is (not) suprisingly similar to the options specification! In this case we use '*' to signify the
start of a new argument definition (rather than the '-' for options). Note, however, that you can actually use '-' if you want to (for example,
you might want to move something that starts as an option but then you decide it would be better as an argument).

The main differences between options and arguments are the specification and the defaults.

Arguments are defined in general as:

    * <name>=<specification>    <Summary>    <optional default setting>
    
    <Description>