On Mon, 11 Jan 2010, Xavi wrote:
Hi,
> ... Ok, I can assume so.
> > return ( HANDLE ) ( ph ? *ph : NULL );
>
> But this assumes that it's always GC.
> Perhaps we need an API function .-
It does not assume anything. It only accepts any pointer items
but I do not see any difference in accepting any GC pointer item
and accepting any pointer item. In both cases the code is not
protected enough and allows to extract some pointer from unknown
pointer item so if later some code will try to use it in some
strict context then it will GPF or cause other bad side effects
like memory corruption.
> BOOL hb_itemIsGC( PHB_ITEM pItem )
> {
> return (pItem && HB_IS_POINTER( pItem ) && pItem->item.asPointer.collect);
> }
Can you explain why information that some item is some unknown
GC pointer item is more usable then it is any pointer item?
For me in both cases it's not sufficient to create any safe code.
> >... will probably cause GPF or other bad side effects.
> IMHO this is always difficult against misuse or indirection of pointers.
> Maybe another kind of runtime type identification could help.
> I don't know now.
Sorry but I do not see any problem so I cannot advice you any solution.
You have to precisely define what you need and why.
best regards,
Przemek
_______________________________________________
Harbour mailing list (attachment size limit: 40KB)
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour
