On Tue, 04 Dec 2007, Mike Evans (Gmail) wrote: > Przemek, > Maybee this will help you. > The container API allows access to the internal data structures of Xbase++. > Each variable in Xbase++ is based internally on a data structure called a > Container object . Each container object manages the type and the value of a > variable. Access to a container is only possible through the ContainerHandle > of the object. [...]
Thank you. I've read yesterday xbase++ C API. Change _con*() in this text to hb_item*() and add in few functions parameter with HB_STACK pointer and you will have very similar API to current one extended for MT mode as we propose. I've even found read/write string item lock functions I wanted to add to Harbour to eliminate hb_itemGetCPtr() :-) In practice in all languages such API will have to be _very_ similar and it's not a problem to define it but rather the decision if we want to make sth like that dropping backward compatibility or not. We will have some time for this decision and I plan to implement 1-st version of MT using current API but then we will have to chose sth. > PS. I'll try to ask a co developer who is working with xBase++ to test it > tomorrow and I'll post the results Thank you again. best regards, Przemek _______________________________________________ Harbour mailing list Harbour@harbour-project.org http://lists.harbour-project.org/mailman/listinfo/harbour
