🚀 go-pugleaf

Hans, thanks for that. I've only just realised what 'Preprocess' means. The 
relevant part of the preprocessed file is as follows

typedef
(int((__stdcall  * LPFN_WSARECVMSG)+((__stdcall  * LPFN_WSARECVMSG)<0 ? -1 : 
1)*0.5))) (
SOCKET s,
LPWSAMSG lpMsg,
LPDWORD lpdwNumberOfBytesRecvd,
LPWSAOVERLAPPED lpOverlapped,
LPWSAOVERLAPPED_COMPLETION_ROUTINE lpCompletionRoutine
);

which looks a bit of a mess. All this is a bit over my head but, at a guess, 
would I be right in saying there are maybe files missing from a header. When 
I try to build the package I'm initially told "Unable to find package 
import: dss.bpi" and "Unable to find package import: ibsmp.bpi" (I clicked 
'Cancel' in respone to both). Is it something to do with that?


"Johannes Weinert" <jw_news@ddbst.de> wrote in message 
news:477626c9@newsgroups.borland.com...
> Hello,
>
> I'm not sure if it helps. If I create a new VCL project and #include 
> <winsock2.h> and <mswsock.h> and preprocess unit1.cpp the typedef expands 
> to:
>
> typedef
> INT
> (__stdcall  * LPFN_WSARECVMSG) (
>  SOCKET s,
>   LPWSAMSG lpMsg,
>        LPDWORD lpdwNumberOfBytesRecvd,
>  LPWSAOVERLAPPED lpOverlapped,
>  LPWSAOVERLAPPED_COMPLETION_ROUTINE lpCompletionRoutine
> );
>
> But I don't see where PASCAL='__stdcall' and FAR='' is defined.
>
> HTH
>
> Hans
>
> Tom Byars wrote:
>> Remy, I searched all my own files for "#define pascal" and "#define far" 
>> and found nothing. I then did the same for all files in the codegear 
>> directory. The only matches I found set pascal as _pascal and far as 
>> _far. So much for bcb 2007. Isn't OOP great. No need to reinvent the 
>> wheel when you can spend 90% of your time trying to fix other peoples.
>>
>> Remy Lebeau (TeamB)" <no.spam@no.spam.com> wrote in message 
>> news:477551c2$1@newsgroups.borland.com...
>>>
>>> "Tom Byars" <tam118118@hotmail.com> wrote in message 
>>> news:477546fd@newsgroups.borland.com...
>>>
>>>> Where would I find these redefinitions Remy?
>>>
>>> You will just have to search all of the header files that your project 
>>> uses. That is why I suggest you output their actual values first to see 
>>> if they have, in fact, been changed by the time mswsock.h is compiled.
>>>
>>>
>>> Gambit
>>>
>>>
>