Re: Re: OOP Access of variables

[simeon2000]

Theo: Thanks, that's a good idea. I just have another question:

If I also have a TArt::Article package data object, and I call the script like this:

package main;

use TArt::Editor;
use TArt::Article;

my $ed = new TArt::Editor;
my $art = new TArt::Article;

If both of these packages (TArt::Editor, TArt::Article) use TArtLib, would they both get the same $dbh object when calling TArtLib->dbh, or would it be two separate TArtLib packages (and thus, two database handle objects)?

[TheoPetersen]

Assuming the code I gave you, there would be only one $dbh. (Hey, that's a catchy phrase ... :)

When learning Perl objects (or Perl anything else), follow your hunches and try them out. You'll develop both knowledge and intuition quickly. That's the nice thing about Perl's learning curve, you can almost always do useful work along the way.

[simeon2000]

Theo: You were right! I forgot that Packages and the object they create are separate. I figured for each Article or Editor I created, there'd be a new $dbh handle, but since it's global in TArtLib, the ref on the $dbh returned the same memory address for both packages' copy of $TArtLib::dbh :) Thanks so much to everyone for help. I learned a lot more about packages and objects today :)

[Masem]

I'd just add in here for clarification of the SoPW poster that $dbh is a reference to your database object (the arrow operator for the DBI functions should be a big tip-off :D); using the "my $dbh = TArtLib->dbh();" anywhere else gains you a local copy fo the reference, but the reference still points to the single copy of the object that holds the DB connection.

---

Dr. Michael K. Neylon - [e-mail] || "You've left the lens cap of your mind on again, Pinky" - The Brain