Fastream Technologies wrote:
> Hello,
>
> Ok when I compare the overbyteicswsocket.hpp's of the working old and
> non-working new v6, I see some differences:
>
> Working:
> virtual int __fastcall Send(Overbyteicswsockbuf::TWSocketData Data,
> int Len)/* overload */;
> virtual int __fastcall SendTo(const sockaddr_in &Dest, int DestLen,
> Overbyteicswsockbuf::TWSocketData &Data, int Len);
>
> Not-Working:
>
> virtual int __fastcall Send(const Overbyteicswsockbuf::TWSocketData
> Data, int Len)/* overload */;
> virtual int __fastcall SendTo(const sockaddr_in &Dest, int DestLen,
> const Overbyteicswsockbuf::TWSocketData Data, int Len);
>
> Notice the "const" in not-working Data param and the reference
> missing in sendto Data!
>
> Thinking thinking... Could a delphi guy can jump in pls?
You found the reason, works without "const" fine in both
Delphi and BCB, it may be required for .NET?
> Best Regards,
>
> SubZero
>
> ----- Original Message -----
> From: "Fastream Technologies" <[EMAIL PROTECTED]>
> To: "ICS support mailing" <twsocket@elists.org>
> Sent: Wednesday, June 27, 2007 2:55 PM
> Subject: Re: [twsocket] New ICS-V6andICS-SSL-V6
> availableBCBCOMPATIBILITYWARNING
>
>
>> Ok, I tried to rename and what's even stranger is no unit compile
>> complained!
>>
>> For instance, Sendto:
>>
>> function WSocket_Synchronized_sendto(
>> s : TSocket;
>> const Buf : TWSocketData;
>> len, flags : Integer;
>> var addrto : TSockAddr;
>> tolen : Integer): Integer;
>> begin
>> if @FSendTo = nil then
>> @FSendTo := WSocketGetProc('sendto');
>> Result := FSendTo(s, Buf^, len, flags, addrto, tolen);
>> end;
>>
>> The definitions in ics winsock.pas are NEVER used! Anyway, they are
>> not the cause of the problem...
>>
>> Regards,
>>
>> SZ
--
To unsubscribe or change your settings for TWSocket mailing list
please goto http://www.elists.org/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be
