Hello Francesco

Francesco Saverio Giudice wrote:
> 
> BTW I'm locked on structure handling. Without a solution on it or 
> without a standardization on passing values it will be a stopping point 
> in hbwin developing.
> I have tried Przemek's proposal, but it's very difficult to handling 
> parameters to/from C code in a standard/easy way.
> Could be use hashes or arrays ( like point[ 'x' ] ) ? but we need some 
> macros to write them fastly at C level (at prg level an object can be
> used).
> I've not tried too much due to lack of spare time.
> Pritpal do you have found a solution ?
> Mindaugas do you have any suggestion ?
> 

No, I tried Przemek's code, which I have already committed in wvgwinc,
but with no results. To write a function for accessing a member of 
a given structure is not the elegant way ( I am not saying - right way ).
Xhb solution seems to fit nicely the way WINAPI implements it. The only
difference being message operator "." vs ":". But it is even better 
because we come from Clipper heritage.

Leave aside the technical part, if we do not devise a better mechanism
to define and access structure, I am afraid a common wrapper for
WINAPI will never see the light of the day.

Przemek, Mindaugus can surely come up with same solution but 
with better internal overhaul of the concept so that the potential
"dangers" discussed can be reduced to bare minimum.

Regards
Pritpal Bedi

-- 
View this message in context: 
http://www.nabble.com/Proposing-hbwhat-for-removal-tp22205966p22210811.html
Sent from the Harbour - Dev mailing list archive at Nabble.com.

_______________________________________________
Harbour mailing list
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour

Reply via email to