LPVOID will normally just expand to void*, and any other pointer type will
be assignable to a void* pointer.
The LP is originally an inherritance from the 16-bit API of Windows 3.11
and below, where you had to differentiate between 16-bit and 32-bit
pointers. We MIGHT see that again in application programs, if someone
takes up the 48-bit far pointers supported by the 386 and higher
processors, but most probably the decision will be to only support > 4GB
for a single process on 64-bit processors. Most existing 32-bit solutions
for more than 4GB memory only lets the OS see all the memory, and limits
each process to less than 4GB.
/Per W
On Mon, 24 Feb 2003, Daniel Glenfield wrote:
>
> I'm looking through some code and I've found a function with the return type
> static LPVOID
>
> static LPVOID SomeFunction()
>
>
> and it has a return value that is an unsigned char*
>
> return MyVal; // An unsigned char*
>
> How does this tally with LPVOID ? Can the return value by a pointer to
> anything if the return type is specified as LPVOID ?
>
>
>
>
> _________________________________________________________________
> Chat online in real time with MSN Messenger http://messenger.msn.co.uk
>
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> Dev-cpp-users mailing list
> Dev...@li...
> TO UNSUBSCRIBE: http://www.noicys.cjb.net/devcpp/ub.htm
> https://lists.sourceforge.net/lists/listinfo/dev-cpp-users
>
|