Re: [twsocket] Two things in ICS (probably bug/potential bug)
The .NET code in V7 is unfinished work, it never compiled. Unfinished work, sure. But it worked at some point. And from trhat point changes have been made with no effort to keep it running because no one seems interested anymore in a .NET version. Ah, now things are clear. Very pity - lots of efforts in vain! Yes indeed. I tought people would be interested in having their Delphi.NET application up and running quickly. It was not the case. Delphi.Net seem to be unuseful thing at all though idea is great. Delphi.NET is now Prism and it is not fully compatible with Delphi.Win32. it is almost impossible to have a single source code for both environment. Havong to source sets is really too much work for me to keep in sync. This was what I made with the Linux/Kylix version and I failed to update Kylix version each time Win32 version was updated. Anyway, Kylix was also a failure but will soon resurect as the next cross platform Delphi version ! It looks like ICS/Kylix could be reused quite easily. -- francois.pie...@overbyte.be The author of the freeware multi-tier middleware MidWare The author of the freeware Internet Component Suite (ICS) http://www.overbyte.be -- To unsubscribe or change your settings for TWSocket mailing list please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
Re: [twsocket] Two things in ICS (probably bug/potential bug)
I was just wondering, creating a DLL in Delphi and use it as described in http://wiki.overbyte.be/wiki/index.php/FAQ._Microsoft_.NET_framework still works or? Regards, Fredrik -Original Message- From: twsocket-boun...@elists.org [mailto:twsocket-boun...@elists.org] On Behalf Of Francois PIETTE Sent: den 2 februari 2011 11:52 To: ICS support mailing Subject: Re: [twsocket] Two things in ICS (probably bug/potential bug) The .NET code in V7 is unfinished work, it never compiled. Unfinished work, sure. But it worked at some point. And from trhat point changes have been made with no effort to keep it running because no one seems interested anymore in a .NET version. Ah, now things are clear. Very pity - lots of efforts in vain! Yes indeed. I tought people would be interested in having their Delphi.NET application up and running quickly. It was not the case. Delphi.Net seem to be unuseful thing at all though idea is great. Delphi.NET is now Prism and it is not fully compatible with Delphi.Win32. it is almost impossible to have a single source code for both environment. Havong to source sets is really too much work for me to keep in sync. This was what I made with the Linux/Kylix version and I failed to update Kylix version each time Win32 version was updated. Anyway, Kylix was also a failure but will soon resurect as the next cross platform Delphi version ! It looks like ICS/Kylix could be reused quite easily. -- To unsubscribe or change your settings for TWSocket mailing list please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
Re: [twsocket] Two things in ICS (probably bug/potential bug)
I was just wondering, creating a DLL in Delphi and use it as described in http://wiki.overbyte.be/wiki/index.php/FAQ._Microsoft_.NET_framework still works or? I guess it won't work anymore with current ICS-V7. -- francois.pie...@overbyte.be The author of the freeware multi-tier middleware MidWare The author of the freeware Internet Component Suite (ICS) http://www.overbyte.be -- To unsubscribe or change your settings for TWSocket mailing list please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
[twsocket] Two things in ICS (probably bug/potential bug)
I just downloaded recent version from SVN and found a strange define in
OverbyteIcsDefs.inc
{$IFDEF CLR}
{$DEFINE BOMB}
{$ELSE}
{$IFNDEF COMPILER7_UP}
{$DEFINE BOMB}
{$ENDIF}
{$ENDIF}
It seems that it shouldn't really be CLR but old versions of BCB or something
else.
And the second thing, I faced with Range check errors inside ICS code. After
some investigations I've found the root of evil: _PostMessage in
TCustomWSocket.Send takes wParam as Integer while FHSocket it is called with
has unsigned type Cardinal. Casting FHSocket to Integer resolved the issue.
There are several other places where socket handle is posted so I think they
should be fixed too. And consider using WPARAM/LPARAM types for casting instead
of general integer ones for higher compatibility.
Moreover, after I've learned some thing regarding x64 I accepted the habit of
sending/posting pointers/handles ONLY in LParam which is what it intended for.
So it'd be nice to see it in ICS.
--
Anton
--
To unsubscribe or change your settings for TWSocket mailing list
please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be
Re: [twsocket] Two things in ICS (probably bug/potential bug)
Anton S. wrote:
I just downloaded recent version from SVN and found a strange define
in OverbyteIcsDefs.inc {$IFDEF CLR}
{$DEFINE BOMB}
{$ELSE}
{$IFNDEF COMPILER7_UP}
{$DEFINE BOMB}
{$ENDIF}
{$ENDIF}
It seems that it shouldn't really be CLR but old versions of BCB or
something else.
It's not for .NET however for Delphi 7+ and BCB 2006+, what is the
problem?
And the second thing, I faced with Range check errors inside ICS
code. After some investigations I've found the root of evil:
_PostMessage in TCustomWSocket.Send takes wParam as Integer while
FHSocket it is called with has unsigned type Cardinal. Casting
FHSocket to Integer resolved the issue.
FHSocket actually is of type TSocket = u_int = Integer defined in
Winsock.pas, WPARAM and LPARAM are of type Integer defined in
Windows.pas, there is no cast required. Do you use Delphi?
And consider using WPARAM/LPARAM types for casting instead of
general integer ones for higher compatibility.
Agreed.
Moreover, after I've
learned some thing regarding x64 I accepted the habit of
sending/posting pointers/handles ONLY in LParam which is what it
intended for. So it'd be nice to see it in ICS.
Currently both WPARAM and LPARAM are 32-bit and will be 64-bit
in x64, no problem IMO.
--
Arno Garrels
--
To unsubscribe or change your settings for TWSocket mailing list
please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be
Re: [twsocket] Two things in ICS (probably bug/potential bug)
It's not for .NET however for Delphi 7+ and BCB 2006+, what is the problem? Do you mean that ICS currently couldn't be compiled under .NET? FHSocket actually is of type TSocket = u_int = Integer defined in Winsock.pas, WPARAM and LPARAM are of type Integer defined in Windows.pas, there is no cast required. Do you use Delphi? Aah, I remembered. I changed Winsock.pas so that TSocket is Cardinal which really is what it should be (U_int is unsigned undoubtedly, and declaring socket as signed is a bug leading to another range check errors in some cases). I hope this bug would sometimes be fixed so it's better to cast it explicitly. Currently both WPARAM and LPARAM are 32-bit and will be 64-bit in x64, no problem IMO. Ok, I didn't know what WPARAM is on x64, tried searching in header files but haven't found the declaration. So if they are identical, no problem here. -- Anton -- To unsubscribe or change your settings for TWSocket mailing list please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
Re: [twsocket] Two things in ICS (probably bug/potential bug)
Anton S. wrote: It's not for .NET however for Delphi 7+ and BCB 2006+, what is the problem? Do you mean that ICS currently couldn't be compiled under .NET? The .NET code in V7 is unfinished work, it never compiled. FHSocket actually is of type TSocket = u_int = Integer defined in Winsock.pas, WPARAM and LPARAM are of type Integer defined in Windows.pas, there is no cast required. Do you use Delphi? Aah, I remembered. I changed Winsock.pas so that TSocket is Cardinal which really is what it should be (U_int is unsigned undoubtedly, and declaring socket as signed is a bug leading to another range check errors in some cases). I hope this bug would sometimes be fixed so it's better to cast it explicitly. I doubt that Winsock.pas will see such a change, it's historical. -- Arno Garrels -- To unsubscribe or change your settings for TWSocket mailing list please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
Re: [twsocket] Two things in ICS (probably bug/potential bug)
It's not for .NET however for Delphi 7+ and BCB 2006+, what is the problem? Do you mean that ICS currently couldn't be compiled under .NET? The .NET code in V7 is unfinished work, it never compiled. Unfinished work, sure. But it worked at some point. And from trhat point changes have been made with no effort to keep it running because no one seems interested anymore in a .NET version. -- francois.pie...@overbyte.be The author of the freeware multi-tier middleware MidWare The author of the freeware Internet Component Suite (ICS) http://www.overbyte.be -- To unsubscribe or change your settings for TWSocket mailing list please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
Re: [twsocket] Two things in ICS (probably bug/potential bug)
Arno wrote: The .NET code in V7 is unfinished work, it never compiled. Francois wrote: Unfinished work, sure. But it worked at some point. And from trhat point changes have been made with no effort to keep it running because no one seems interested anymore in a .NET version. Ah, now things are clear. Very pity - lots of efforts in vain! Delphi.Net seem to be unuseful thing at all though idea is great. -- Anton -- To unsubscribe or change your settings for TWSocket mailing list please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
