> Speaking about documentation i'd said we must document usage of every > public > interface and specify explicitly how instance is constructed and destroyed. >
Well - with this adjustment I can agree with every style. (Though must say that addRef/release pair in our interfaces is already far-far away from how it's used in things like OLE2. Do you want to rename them?) > PS You make me remember MS way to report errors in their DAC's. They have > global > Errors collection and it must be checked after every call of any object. Or > remember > GetLastError. Do you want something similar ? We can remove IStatus parameter > from every method and add > > IStatus* IMaster::getStatus() > > to the master interface. Not sure i like it... Definitely dislike. This looks VERY bad from MT POV. What if one wants to check for errors in the thread distinct from that in which function was called? (I know it looks strange, but we really had such a case with SAS). That's all are errno-like variations, and people used to have problems with errno in MT world, and why should we once again repeat all that steps? ------------------------------------------------------------------------------ Achieve unprecedented app performance and reliability What every C/C++ and Fortran developer should know. Learn how Intel has extended the reach of its next-generation tools to help boost performance applications - inlcuding clusters. http://p.sf.net/sfu/intel-dev2devmay Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
