|
Module::Release::SVK::ConfigData - Configuration for Module::Release::SVK |
Module::Release::SVK::ConfigData - Configuration for Module::Release::SVK
use Module::Release::SVK::ConfigData;
$value = Module::Release::SVK::ConfigData->config('foo');
$value = Module::Release::SVK::ConfigData->feature('bar');
@names = Module::Release::SVK::ConfigData->config_names; @names = Module::Release::SVK::ConfigData->feature_names;
Module::Release::SVK::ConfigData->set_config(foo => $new_value); Module::Release::SVK::ConfigData->set_feature(bar => $new_value); Module::Release::SVK::ConfigData->write; # Save changes
This module holds the configuration data for the Module::Release::SVK
module. It also provides a programmatic interface for getting or
setting that configuration data. Note that in order to actually make
changes, you'll have to have write access to the Module::Release::SVK::ConfigData
module, and you should attempt to understand the repercussions of your
actions.
config($name)undef if no such item exists.
feature($name)undef if no such feature exists.
Data::Dumper. This includes references, objects (usually), and
complex data structures. It probably does not include transient
things like filehandles or sockets.
config_names()Module::Release::SVK::ConfigData, or in scalar context the number of items.
feature_names()Module::Release::SVK::ConfigData, or in scalar context the number of features.
auto_feature_names()write()set_config() and set_feature() to disk.
Requires write access to the Module::Release::SVK::ConfigData module.
Module::Release::SVK::ConfigData was automatically created using Module::Build.
Module::Build was written by Ken Williams, but he holds no
authorship claim or copyright claim to the contents of Module::Release::SVK::ConfigData.
|
Module::Release::SVK::ConfigData - Configuration for Module::Release::SVK |