I can only echo Stanislav's question: in an interpreted scripting
environment, what necessity is there for static properties? If static
properties are a "must" in a program then I would strongly suggest you
relook at your program architecture.
I can´t imagine what you dislike about retrieving information on classes, I really don´t want to create an example again, because it won´t be realized at the moment, but imagine this case:
1)You´ve got *a lot* of classes.
2)They´re not all yours, but they follow several specifications eg. including information about themselves in properties to be easily portable.
3)You want to access this information, but you can´t if not instanciating the class - you´ll have to either build a) objects that contain information about a collection of classes [then you´ve again new objects you need to fiddle around with] b)instanciate the particular class and access the property [low-speed solution]
Perhaps it´s not a good example, but don´t tell me that I *could* save this information into a file, into an array or db or somewhat else, I know and that´s not the point - every intermediate+ programmer will find workarounds for everything - it´s just sometimes handy to access these properties.
regards
ps. let´s end this thread now
--
o----------0-¬---------O-·---¬----o---®-----o o O ° .
| http://www.kiffen.de | pRoteçt y0ur bRaín |0 O ° ¤ °
·
0°·³°²'²³-¹'³´³°^°³~³²³°'³²²¨³²^³¹³²°²³`³º³°Þ °
o © ° . ·
| psychedelic experience | gott@kiffen.de | O ° o °
o-¬--o--0-----©-·--O-----o-----0-¤----------o 0 ° · ° . ¤ ·