That's cool it worked for you.
I have 1 last idea, put the get_class_var() function in a debug type rutine and call it from it own function withing the class.
like:
$someclass -> debug_show_current_class_var();
<i>AFTER</i> you have allready intialized those functions .
Example: I am building a class version of PHPNUKE. And I create config classes for each module (forums, vote, ect.) within this module <B> ALL </B> data is contained in <B>1</B> multi-array. So for each attrib of that array I give the it a definition so it is <I>INITiALIZED</I> <B>AND</B> documented at the same time!
example:
class config
{
arr_config = array (
'DBhost' => array (
'value' => "localhost",
'description' => "The host
for the database"
);
);
}
------------------------------------
accesed like so:
------------------------------------
class someclass extends config
{
function debug_show_current_class_var()
{
temp .= <BR>;
temp .= get_class_var(this -> arr_config);
// echo or retun temp
return(temp);
}
$go = new someclass ();
echo $go -> debug_show_current_class_var();
Extremly difficult to concieve; before I fully understood it, but the pay off is like purchasing <B>BOARDWALK</B> in a game of monopoly! Once you get around to it, game over.
All relevent code is thus kept in a central place and documentaion is BUILT INTO the array with relativly <i> little </i> overhead or speed sacrifice.
Using this concecept my script slowed about .09 of a second (really) and the pay-off is HUGE!
Hope this helps! (*looks a few letters back) lol, I got excited huh?
Good luck -- let me know how it turns out,
COPE