comment on

So, in a nutshell, your objects of class "Thing" contain the class name of the back end class, in the hash member $x->{backend}. As far as I am concerned, this is perfectly acceptable.

There may be alternatives, if for instance you actually need to have (and keep track of) an object blessed into the back end class, associated with the "Thing" object. In this case, you would just store a reference to this object (you can then get its class name using ref if you really want it).

Another alternative is the factory pattern, where method calls in your "Thing" class spit out backend objects given parameters, etc.

It's a case of TIMTOWDI.

--
I'm Not Just Another Perl Hacker

In reply to Re: how do you call this? $x->bar(); by rinceWind
in thread how do you call this? $x->bar(); by dada

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


No such thing as a small change
	PerlMonks