"rc" <> wrote in news:1101076183.352311.218570
@f14g2000cwb.googlegroups.com:
> 1. Write a singleton class/module that will create/hold a file handle
> to do logging (I found a singleton example in an old "ThePerlReview").
> This way all the other modules I write can simply call methods this
> object to do logging. -- Is this a good idea, how is it done in the
> real world so all modules can write to the same log?
http://search.cpan.org/~mschilli/Log...og/Log4perl.pm
among others
> 2. Write a class/module that will read a configuration file in a
> generic way (so like the logging class, I can reuse it for other
> projects). This way I can call get/set... methods, I've seen a great
> generic example in "Object Oriented Perl" for the get/set part. -- I
> want to do this instead of sourcing in a hash so it can check that
> valid methods are being called.
http://search.cpan.org/~kane/Config-...Config/Auto.pm among
others
> 3. Write a wrapper around Net::FTP that will catch exceptions and
> retry login/put/get if time outs occur. This class will use the
> logging singleton class to write to the same filehandle that the main
> application and all other modules are witting too.
If you so wish ...
> 4. The actual application will use these modules and setup the logging
> singleton.
OK.
--
A. Sinan Unur
d
(remove '.invalid' and reverse each component for email address)