| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | 16-Bit To 32-Bit Callbac |
Thanks Wim Veldhuis for your msg about 16-Bit To 32-Bit Callbac, on Monday, 11-14-1994! WV> Just out of curiosity, I used to think that the above syntax is WV> just used to tell the compiler that the bytes starting at the WV> address symbolized by p16Pointer have to be interpreted as a void * WV> WITHOUT any altering of those bytes. Since OS/2 specifies special WV> API functions to convert pointers this would not be Actually the bytes pointed to are irrelevant. The whole casting thing changes the content of the pointer itself, from a flag 32 bit offset to a segmented address. I really does not seem worth it to provide APIs in a way since all points have types that indicate whether they are 16/32, so just doing an assignment from one type to another causes the cast implictly. Maybe the APIs are just for other languages that don't provide the kind of smarts that CSet/2++ does. ___ X KWQ/2 1.2b X This tagline stolen by KWQ Mail/2. --- Maximus/2 2.02* Origin: Fernwood - your source for OS/2 files! (1:141/209) SEEN-BY: 12/2442 54/54 620/243 624/50 632/348 640/820 690/660 711/409 410 413 SEEN-BY: 711/430 807 808 809 934 942 949 712/353 623 713/888 800/1 @PATH: 141/209 270/101 396/1 3615/50 229/2 12/2442 711/409 54/54 711/808 809 @PATH: 711/934 |
|
| SOURCE: echomail via fidonet.ozzmosis.com | |
Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.