Hi Pritpal,

>    + Implemented to avoid use of QT_PTROF() and QT_PTROFXBP() macros.
>      The functionality is transparent and accepts HBQT and HBXBP objects
>      as is. 
Thank you very much.

>      TODO: Method SomeQtClass:new( ... ) 
>               ::pPtr := QSomeClass( ... )
>            In above construct it is not known how many parameters
>            are of type pointer and otherwise and how, if resolved, 
>            be forwarded to Qt wrapper with (...) syntax.

Again maybe I'm missing something, but in this 
case isn't the pointer unwrapping done by inside 
QSomeClass() ? I mean if you pass parameters 
as is, why would you need to make any transformations 
on them, when this transformation can be done 
at destination function.

IOW it's shouldn't be caller's responsibility 
to resolve any such internal details, and current 
patch seemed to have addressed just that, so 
maybe it's already okay.

Brgds,
Viktor

_______________________________________________
Harbour mailing list (attachment size limit: 40KB)
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour

Reply via email to