Hi,
Current code is very short and simple. At least I understand it so far ;-)
The simplicity was the main goal, after I found original OLE is not working (it was xHarbour times) and I was unable to understand some implementation ideas.
1. Empty date in hbwin TOLEAUTO is send as VT_NULL. Should we replicate it?
Well, it would be nice to hear OLE users opinion. Does OLE has EMPTY DATE, etc.?
2. HB_IT_POINTER support. Should we add it?
If we put some objects, etc, into untyped pointer it is not very good idea, but may be it could be useful in some case. Does anyone uses such features?
3. Array support. Should we add it?
It would be a feature. Does anybody have some sample code using OLE arrays?
4. OLECREATEOBJECT() and OLEGETACTIVEOBJECT() return simple pointer item. Maybe we should change it to GC pointer item. In such case we can eliminate destructor from HB_OLEAUTO class. OLERELEASE() will also not be longer necessary though we can leave it to force releasing OLE objects even if some other references still exists.
I'll add it.
5. The hbwin TOLEAUTO class supports iteration by FOR EACH loop. Should we add it too?
I've looked to hbwin OLE code. Each object uses ::pOleEnumerator to store enumerator. It is not very good solution, since we can have a few FOR EACH loops inside each other for the same object. I'll try to find a better way of implementation. Do we have any FOR EACH sample code for OLE?
6. Should we add passing parameters by reference?
Any sample code?
7. The exit code should be fixed to avoid problems executing destructors after hb_ole_exit(). 8. s_lOleError should be thread local to make it MT safe.
I see it is already implemented. Thank You. Regards, Mindaugas _______________________________________________ Harbour mailing list [email protected] http://lists.harbour-project.org/mailman/listinfo/harbour
