Scroll to navigation

Sendpage::KeesConf(3pm) User Contributed Perl Documentation Sendpage::KeesConf(3pm)


Sendpage::KeesConf - implements a configuration file reader


    use Sendpage::KeesConf;
    $config = Sendpage::KeesConf->new();
    $config->define("variable", { DEFAULT => "setting" });


I have borrowed VERY heavily from Andy Wardley's ( "AppConfig" tool, which can be found on CPAN ( but I found it not dynamic enough for multi-instance variable defaults. As a result, I wrote this massively trimmed-down version for my use.

The following methods are available:

$config = Sendpage::KeesConf->new();
The constructor doesn't take an arguement, but it should in the future.
This call will make $config forget about any variables it has loaded. It does NOT forget "define"d variables, just instantiated ones via "file".
$config->define($name, $options);
This will define a variable by the name of $name.

$options can contain:

What type of variable this should be. Default value is "1". The available types are:
Boolean (true/false, yes/no, 1/0)
Scalar (any string)
List (an array of strings)
The default value the variable should have if it is not overridden during the call to "file". The DEFAULT must be the same data type as ARGCOUNT. The default DEFAULT is the string "<unset>".
set this to 1 if you want the default value to be undefined. This is a hack to get around the default DEFAULT.
This tests to see if there is a section loaded named $name
This call will search for the variable named $name. If it is not found, it will return undef. If the value exists, it will return the value. This is a way to call "get" without having a default passed through.
This call will search for the variable named $name. If it is not found, it will return false. If the value exists, it will return true. This is a way for the user to find out if they will get a "default" on a call to "get".
This call will search for the variable named $name. If it is not found, the section portion will be removed, and retried for a sectionless "get" call.

That way, global variables can be overridden by section-specific variables. If "SECTION:Instance@name" does not exist, "name" will be tried.

This call will search for the variable named $name. If it is not found, it will fall back to the default for the section. Sections are explained in more detail later.
Returns an array of the names of all the variables in the class $class.
Loads variables from the named file. Syntax for this file is:


If VARIABLE is an array, VALUE is loaded using commas (,) as the list separator. The variable will be available under the name of the section. For example, to see VALUE2, it would be accessed as:


Notice, that "=", ":", and "@" are all not allowed in section or variable names.

Sections can be defined (and loaded) so that defaults can pass back to a defined section default. For example, lets say that you have several modems, and most of them have different settings. You can define all the modem variables like so:

        $config->define("modem:baud",{ DEFAULT => 9600 });
        $config->define("modem:flowctl",{ DEFAULT => "hardware" });

Then, when you load them, let's say the config file has:

        baud = 115200

The baud rate for the sportster will come back as 115200, but the hayes will fall back during a "get" call, and find the default for the modem section: 9600. Both fallback to have "flowctl" as "hardware":

    # returns specific value 115200
    # returns default value 9600
    # both return default value "hardware"


As mentioned above, variable names (and section names) cannot have the characters ":", "@", or "=" in them.
There should be a way to pass default defaults into "new". That would be handy, and could eliminate the need for the UNSET option in "define".


Kees Cook <>


perl(1), sendpage(1), Sendpage::KeesLog(3), Sendpage::Modem(3), Sendpage::PagingCentral(3), Sendpage::PageQueue(3), Sendpage::Page(3), Sendpage::Recipient(3), Sendpage::Queue(3)


Copyright 2000 Kees Cook.

This library is free software; you can redistribute it and/or modify it under the same terms as Perl itself.


Hey! The above document had some coding errors, which are explained below:

Expected text after =item, not a number
Expected text after =item, not a number
2021-01-08 perl v5.32.0