Home  |  Linux  | Mysql  | PHP  | XML
From:Steve Bertrand Date:Sun Jun 28 23:20:08 2009
Subject:Using common object, without passing it around
Can anyone suggest a perldoc or recommended practise that will help me
in regards to:

I have numerous classes, all suited to a different object-type or function.

When I instantiate an object (all classes are under the same Module::
umbrella), I *think* what I want to do is create an 'error' object, but
I want that _specific_ instance of the Error object carried along with
ALL objects created during the time the life-cycle is in operation.

This way, I believe that I can build Sanity checks into objects from
certain classes, and these Sanity checks will ALWAYS work on the same
Error object.

How can I do this sort of thing, without having to 'pass around' the
Error object?

Is it time that I look deeper into inheritance, and create inheritable
instantiation methods in a base class?

Steve

Navigate in group perl.beginners at sever nntp.perl.org
Previous Next


Your recent visits
Re: floating point precision
Re: Rendering data structures using CGI::Application
help on example from "mastering algorithm with perl" on binary search
Re: Manipulating the symbol table
script for shutdown remote machine



  
© No Copyright
You are free to use Anything, but please consult your advocate before doing so as this website
also list content from other sources which may be copyrighted.
Site Maintained by Zareef Ahmed
Powered By PHP Consultants