Re: app design issue

the current trick to fake static variables is usually use semi-private globals.. as below using _CLASS_NAME to associate them with the classes using singleton method calls is expensive if you have to fetch the object alot on a page.. Regards Alan Robin Ericsson wrote:

I have this setup: class A constructor()

    b = new Class B     b->run();

$GLOBALS['_CLASS_B']['db'] = null;

class B run()

global $_CLASS_B;

    db = new PEAR::DB

$_CLASS_B['db'] = new PEAR::DB

$db = &$_CLASS_B['db']

    do db stuff
    if (specialoccasion)
      c = new Plugin
      c->run()
  class C

Does everybody understand this? My problem is that class also needs to use the db object in class C. I could pass the db object on the class C as I do it today, but it doesn't look nice to do it. Should it place as a global object? Singleton? best regards Robin