MidgardReflectionProperty ( was MidgardObjectProperty )
Piotras <pp-VVDi8QVAvoBWk0Htik3J/[email protected]>
| Newsgroups | gmane.comp.web.midgard.devel |
|---|---|
| Message-ID | <[email protected]> |
Hi! I started to fix http://midgard.tigris.org/issues/show_bug.cgi?id=94. This "cleanup" ( change ) is mandatory to make Midgard reflection features much more effective and much faster. I asked Torben today if MidgardReflectionProperty class name isn't much more better than MidgardObjectProperty name for this functionality. We both agreed to make MidgardReflectionProperty which is much more descriptive and intuitive. Reflection should be very easy to implement after all changes I made in schema and objects's code. However , Torben asked a very good question: <#midgard> Piotras torben: so you should use get_class_vars and MidgardReflectionProperty torben the problem is, that get_class_vars is not neccessarily identical to the properties defined in the schema. torben ever thought of extended classes? </#midgard> So , here I have few questions: 1. How to handle properties which are members of child classes? For example return false for function which returns bool and property is not found in schema class? Or make special exceptions and trigger some warnings or errors? ( which comes down to neverending errors checks ) 2. Who and where should be responsible for getting base classes' names? Schema class name should be retrieved on language binding level? ( like it is done in midgard-php ) Or caller should be responsible to retrieve correct class name before using it as function parameter? Piotras