Hello
<<<
Thanks, I think you should look at it, the other thing is GC
collected pointers which is essential for a lot of tasks here.
I'd suggest to try it, it's not that bad believe me.
>>>
I tried it after posting above message. But I get only
pointers at PRG level which I cannot exploit there.
If we go by that way, then I am afraid we need to write
a lot of code just to streamline numerous structures.
I will show an example next post.
>1) You're introducing xhb dependency for gtwvg, which isn't good.
As stated in previous post, I have deffered this decision.
So until we reach an agreement WAPI_*() functions category
will contain only those functions not needing structures.
>2) Problem reports of gtwvg problems are ignored.
Which reports ? Any list? Except that there are type mismatches
on some other compilers which I do not use. Please post
(everybody) the problems so those could be fixed.
<<<
3) Instead of moving useful and existing WAPI functionality from
existing libs to hbwin, you're adding plain new ones.
Which is by itself not a problem, currently messes situation
just gets even more messed by growing another branch
here without touching the numerous existing ones.
>>>
This is the next step. Right now I write only those functions
needed for WVG*() classes. Thses functions will be UNICODE
compliant and are under testing env. To remove those from
other libs will be quite fast, then.
<<<
As a final effect it seems that we're growing another hbwhat
lib, and not getting closer to a well laid and unified Windows
interface.
At least, that's how it looks from here so far.
>>>
Surely not. Not even interested in that direction.
Regards
Pritpal Bedi
--
View this message in context:
http://www.nabble.com/SF.net-SVN%3A-harbour-project%3A-10342--trunk-harbour-tp22092017p22096767.html
Sent from the Harbour - Dev mailing list archive at Nabble.com.
_______________________________________________
Harbour mailing list
[email protected]
http://lists.harbour-project.org/mailman/listinfo/harbour
