in reply to Prior art reference, and comment
in thread Perl Programming guidelines/rules

How many systems are you backing up Bill the Anonymous Monk ? Are you going to deploy the script to every corner of the network, hack the configuration each time? What happens when the script is revised ? Magically diff the code updates from the variable hacks and then what. The OO call to Backup.pm could easily be a single config file. Update the module often as you like , all the config stays where it should be.

Backup->new( "/etc/sys-backup.cfg" );

If I've typed it twice already, how many more times today before I make it a method? $self->grumpy_reply(\$parent) : )

Replies are listed 'Best First'.
Re: Prior art reference, and comment
by Abigail-II (Bishop) on Nov 22, 2002 at 14:10 UTC
    What, you really think OO is the only way to archieve this? Don't be silly. 
        use Backup;
    Backup::doit config => "/etc/sys-backup.cfg";

    [download]

    works as well as an OO-wrapper.

    I've written backup programs in Perl as well. It did use a configuration file, and the functionality was changed without the need to change the interface. And guess what? It wasn't OO!

    Abigail

[reply]
[d/l]

In Section Meditations