Hi Przemek,
Yes, it is. Anyhow accepting unknown pointer items is also wrong and I do not want to add to core code functions which are not usable for code which cleanly checks all pointer items.
Yes I see it. Thank you for teach me to see.
It can be done in few different ways, i.e. you can add public function which will operate on on different pointer items, or you can implement some casting or aliasing mechanism like the one I sent as example for HBQT few months ago. Looks that it creates problems for different developers so maybe in some spare time I'll try to add template code or some very basic HVM support for GC pointer item aliasing which should help in such situations.
I read the example and no problem to wait for more. IMHO GC is one of the most important part of Harbour, I think it's better when more clear is the use and implementation. It can also facilitate the adaptation of 3rd party libraries that now use mostly plain pointers.
Maybe I'll join it with OOP support for GC pointer items which is still on my TODO list.
[ Yep! in C ... sorry, this excites me and brings back memories :) ] Best regards, Xavi _______________________________________________ Harbour mailing list (attachment size limit: 40KB) Harbour@harbour-project.org http://lists.harbour-project.org/mailman/listinfo/harbour
