https://www.excelfox.com/forum/showt...age4#post17896
https://www.excelfox.com/forum/showt...age4#post17896
From here on are intermediate experiments and considerations on VB strings in the win32 api
This post just has temporary notes for me so will be of no interest to anyone, or might be later. It may be a first attempt by me at some conclusions, with references that may be reproduced later better or help me to navigate better in my later conclusions
From here on are intermediate experiments and considerations/ conclusion attempts on VB strings in the win32 api
Consideration of the two typical forms of most api functions ( the WUnicorn and the AASI )
Consideration of the two typical forms of most api functions involving strings ( the MyAPIFunctionWUnicorn and the MyAPIFunctionAASI ) helps also to understand what’s going on with strings in the win32 api
For the time being, the difference between the the WUnicorn and the AASI can be considered as related some how the "WUnicorn AASI discussions in posts such as https://www.excelfox.com/forum/showt...ll=1#post24946 and previous
https://eileenslounge.com/viewtopic....324730#p324730
Api knows nothing about VB(A) strings…. If we restrict ourselves to the time from win32 api, then to all intents and purposes the
Reply With Quote
Bookmarks