Re: [twsocket] Problem with v6 BCB package
What is your suggestion then? Continue to search how to turn on/off the definitions which are problematic with BCB6. -- [EMAIL PROTECTED] http://www.overbyte.be - Original Message - From: Fastream Technologies [EMAIL PROTECTED] To: ICS support mailing twsocket@elists.org Sent: Wednesday, March 01, 2006 10:40 AM Subject: Re: [twsocket] Problem with v6 BCB package What is your suggestion then? Regards, SubZ I don't like this idea. -- [EMAIL PROTECTED] http://www.overbyte.be - Original Message - From: Fastream Technologies [EMAIL PROTECTED] To: ICS support mailing twsocket@elists.org Sent: Tuesday, February 28, 2006 7:58 AM Subject: Re: [twsocket] Problem with v6 BCB package Francois, I think we should remove the library and types units and embed the code into other units with direct Windows names. OR BETTER, we can rename the functions as ICSGetWindowLong() and ICSHWND. I can do this for you but I want to be assured that my changes will be applied and therefore I would not have to do it every time a new version comes out. Regards, SZ - Original Message - From: Dan [EMAIL PROTECTED] To: ICS support mailing twsocket@elists.org Sent: Monday, February 27, 2006 11:51 PM Subject: Re: [twsocket] Problem with v6 BCB package I didn't think #defines followed namespaces, thought they were always global. Could be wrong... Dan - Original Message - From: Fastream Technologies [EMAIL PROTECTED] To: ICS support mailing twsocket@elists.org Sent: Monday, February 27, 2006 2:19 PM Subject: Re: [twsocket] Problem with v6 BCB package NO wait, you must have got the idea of how to make a namespace from delphi: it is easy and done in all ICS code as it is automatic in Delphi! In Delphi the unit name becomes the namespace name in C++! The problem is in the current situation you -somehow- make the namespace contents public and that causes ambigouity with windows identifiers. We need to either: 1) make the namespace private and calls like OverbyteIcs::getwindowlong OR 2) find a way to remove the namespace from within C++ source code. For example: #include vcl.h #include overbyteicshttpsrv.hpp do NOT use namespace overbyteICS // not sure the syntax here! #include winsock.h Regards, SZ - Original Message - From: Francois Piette [EMAIL PROTECTED] To: ICS support mailing twsocket@elists.org Sent: Monday, February 27, 2006 4:00 PM Subject: Re: [twsocket] Problem with v6 BCB package I have no idea about how to define C++ name space with Delphi code. -- [EMAIL PROTECTED] http://www.overbyte.be - Original Message - From: Fastream Technologies [EMAIL PROTECTED] To: ICS support mailing twsocket@elists.org Sent: Monday, February 27, 2006 2:47 PM Subject: Re: [twsocket] Problem with v6 BCB package No I don't think that would be easy as well... Why don't you use namespaces which are designed for this purpose? You should not include the pascal translation of, use namespace overbyte; instead call functions like Overbyte::getwindowLong(); I understand that you wanted to simply the uses part of the package but this makes it further complicated in the projects. Regards, SZ - Original Message - From: Fastream Technologies [EMAIL PROTECTED] To: ICS support mailing twsocket@elists.org Sent: Monday, February 27, 2006 3:43 PM Subject: Re: [twsocket] Problem with v6 BCB package This won't be as easy as to say: There are 20+ units! What about including a special .h for this purpose that undefs all overbyte defs?? Regards, SZ - Original Message - From: Francois Piette [EMAIL PROTECTED] To: ICS support mailing twsocket@elists.org Sent: Monday, February 27, 2006 3:23 PM Subject: Re: [twsocket] Problem with v6 BCB package #ifdef HWND #undef HWND #endif Put this code (and similar) before the ICS includes. Also try varying the include order between ICS and Windows. -- [EMAIL PROTECTED] http://www.overbyte.be - Original Message - From: Fastream Technologies [EMAIL PROTECTED] To: ICS support mailing twsocket@elists.org Sent: Monday, February 27, 2006 2:04 PM Subject: Re: [twsocket] Problem with v6 BCB package Hello, - Original Message - From: Francois Piette [EMAIL PROTECTED] To: ICS support mailing twsocket@elists.org Sent: Monday, February 27, 2006 12:56 PM Subject: Re: [twsocket] Problem with v6 BCB package I have been able to skip the bug by removing zlibobjs.pas. :-) Now there is a huge design problem: Problems are always huge with you
Re: [twsocket] Problem with v6 BCB package
It is not just about my project! I create an empty project, drop a v6 httpserver component and it gives the same result! If you look at the vcl.components.using group of borland, you will see that the responses (including Remy from TeamB), there is no such way to uninclude/exclude a header in C++. I skimmed through the Stroustrup book and it's the same!! I think we need to rename the overriding functions with a prefix such as Ics. Regards, SZ - Original Message - From: Francois Piette [EMAIL PROTECTED] To: ICS support mailing twsocket@elists.org Sent: Wednesday, March 01, 2006 12:05 PM Subject: Re: [twsocket] Problem with v6 BCB package What is your suggestion then? Continue to search how to turn on/off the definitions which are problematic with BCB6. -- [EMAIL PROTECTED] http://www.overbyte.be - Original Message - From: Fastream Technologies [EMAIL PROTECTED] To: ICS support mailing twsocket@elists.org Sent: Wednesday, March 01, 2006 10:40 AM Subject: Re: [twsocket] Problem with v6 BCB package What is your suggestion then? Regards, SubZ I don't like this idea. -- [EMAIL PROTECTED] http://www.overbyte.be - Original Message - From: Fastream Technologies [EMAIL PROTECTED] To: ICS support mailing twsocket@elists.org Sent: Tuesday, February 28, 2006 7:58 AM Subject: Re: [twsocket] Problem with v6 BCB package Francois, I think we should remove the library and types units and embed the code into other units with direct Windows names. OR BETTER, we can rename the functions as ICSGetWindowLong() and ICSHWND. I can do this for you but I want to be assured that my changes will be applied and therefore I would not have to do it every time a new version comes out. Regards, SZ - Original Message - From: Dan [EMAIL PROTECTED] To: ICS support mailing twsocket@elists.org Sent: Monday, February 27, 2006 11:51 PM Subject: Re: [twsocket] Problem with v6 BCB package I didn't think #defines followed namespaces, thought they were always global. Could be wrong... Dan - Original Message - From: Fastream Technologies [EMAIL PROTECTED] To: ICS support mailing twsocket@elists.org Sent: Monday, February 27, 2006 2:19 PM Subject: Re: [twsocket] Problem with v6 BCB package NO wait, you must have got the idea of how to make a namespace from delphi: it is easy and done in all ICS code as it is automatic in Delphi! In Delphi the unit name becomes the namespace name in C++! The problem is in the current situation you -somehow- make the namespace contents public and that causes ambigouity with windows identifiers. We need to either: 1) make the namespace private and calls like OverbyteIcs::getwindowlong OR 2) find a way to remove the namespace from within C++ source code. For example: #include vcl.h #include overbyteicshttpsrv.hpp do NOT use namespace overbyteICS // not sure the syntax here! #include winsock.h Regards, SZ - Original Message - From: Francois Piette [EMAIL PROTECTED] To: ICS support mailing twsocket@elists.org Sent: Monday, February 27, 2006 4:00 PM Subject: Re: [twsocket] Problem with v6 BCB package I have no idea about how to define C++ name space with Delphi code. -- [EMAIL PROTECTED] http://www.overbyte.be - Original Message - From: Fastream Technologies [EMAIL PROTECTED] To: ICS support mailing twsocket@elists.org Sent: Monday, February 27, 2006 2:47 PM Subject: Re: [twsocket] Problem with v6 BCB package No I don't think that would be easy as well... Why don't you use namespaces which are designed for this purpose? You should not include the pascal translation of, use namespace overbyte; instead call functions like Overbyte::getwindowLong(); I understand that you wanted to simply the uses part of the package but this makes it further complicated in the projects. Regards, SZ - Original Message - From: Fastream Technologies [EMAIL PROTECTED] To: ICS support mailing twsocket@elists.org Sent: Monday, February 27, 2006 3:43 PM Subject: Re: [twsocket] Problem with v6 BCB package This won't be as easy as to say: There are 20+ units! What about including a special .h for this purpose that undefs all overbyte defs?? Regards, SZ - Original Message - From: Francois Piette [EMAIL PROTECTED] To: ICS support mailing twsocket@elists.org Sent: Monday, February 27, 2006 3:23 PM Subject: Re: [twsocket] Problem with v6 BCB package #ifdef HWND #undef HWND #endif Put this code (and similar) before the ICS includes. Also try varying the include order between ICS and Windows. -- [EMAIL PROTECTED] http://www.overbyte.be
Re: [twsocket] Problem with v6 BCB package
I don't like this idea. -- [EMAIL PROTECTED] http://www.overbyte.be - Original Message - From: Fastream Technologies [EMAIL PROTECTED] To: ICS support mailing twsocket@elists.org Sent: Tuesday, February 28, 2006 7:58 AM Subject: Re: [twsocket] Problem with v6 BCB package Francois, I think we should remove the library and types units and embed the code into other units with direct Windows names. OR BETTER, we can rename the functions as ICSGetWindowLong() and ICSHWND. I can do this for you but I want to be assured that my changes will be applied and therefore I would not have to do it every time a new version comes out. Regards, SZ - Original Message - From: Dan [EMAIL PROTECTED] To: ICS support mailing twsocket@elists.org Sent: Monday, February 27, 2006 11:51 PM Subject: Re: [twsocket] Problem with v6 BCB package I didn't think #defines followed namespaces, thought they were always global. Could be wrong... Dan - Original Message - From: Fastream Technologies [EMAIL PROTECTED] To: ICS support mailing twsocket@elists.org Sent: Monday, February 27, 2006 2:19 PM Subject: Re: [twsocket] Problem with v6 BCB package NO wait, you must have got the idea of how to make a namespace from delphi: it is easy and done in all ICS code as it is automatic in Delphi! In Delphi the unit name becomes the namespace name in C++! The problem is in the current situation you -somehow- make the namespace contents public and that causes ambigouity with windows identifiers. We need to either: 1) make the namespace private and calls like OverbyteIcs::getwindowlong OR 2) find a way to remove the namespace from within C++ source code. For example: #include vcl.h #include overbyteicshttpsrv.hpp do NOT use namespace overbyteICS // not sure the syntax here! #include winsock.h Regards, SZ - Original Message - From: Francois Piette [EMAIL PROTECTED] To: ICS support mailing twsocket@elists.org Sent: Monday, February 27, 2006 4:00 PM Subject: Re: [twsocket] Problem with v6 BCB package I have no idea about how to define C++ name space with Delphi code. -- [EMAIL PROTECTED] http://www.overbyte.be - Original Message - From: Fastream Technologies [EMAIL PROTECTED] To: ICS support mailing twsocket@elists.org Sent: Monday, February 27, 2006 2:47 PM Subject: Re: [twsocket] Problem with v6 BCB package No I don't think that would be easy as well... Why don't you use namespaces which are designed for this purpose? You should not include the pascal translation of, use namespace overbyte; instead call functions like Overbyte::getwindowLong(); I understand that you wanted to simply the uses part of the package but this makes it further complicated in the projects. Regards, SZ - Original Message - From: Fastream Technologies [EMAIL PROTECTED] To: ICS support mailing twsocket@elists.org Sent: Monday, February 27, 2006 3:43 PM Subject: Re: [twsocket] Problem with v6 BCB package This won't be as easy as to say: There are 20+ units! What about including a special .h for this purpose that undefs all overbyte defs?? Regards, SZ - Original Message - From: Francois Piette [EMAIL PROTECTED] To: ICS support mailing twsocket@elists.org Sent: Monday, February 27, 2006 3:23 PM Subject: Re: [twsocket] Problem with v6 BCB package #ifdef HWND #undef HWND #endif Put this code (and similar) before the ICS includes. Also try varying the include order between ICS and Windows. -- [EMAIL PROTECTED] http://www.overbyte.be - Original Message - From: Fastream Technologies [EMAIL PROTECTED] To: ICS support mailing twsocket@elists.org Sent: Monday, February 27, 2006 2:04 PM Subject: Re: [twsocket] Problem with v6 BCB package Hello, - Original Message - From: Francois Piette [EMAIL PROTECTED] To: ICS support mailing twsocket@elists.org Sent: Monday, February 27, 2006 12:56 PM Subject: Re: [twsocket] Problem with v6 BCB package I have been able to skip the bug by removing zlibobjs.pas. :-) Now there is a huge design problem: Problems are always huge with you. In OverbyteIcsTypes.pas, you redefined all the types used from windows for compactibality reasons (I believe). However BCB complains (in project with overbyteics package, not in package compilation itself!) there is ambiguity in types and functions such as getwindowlong and HWND and almost all of them! Any idea what can fix it? Maybe add #undef after the units which define them ? Either undefine those symbol from the standards units or from ICS units. Can you give a C++ example? I have code like: #include vcl.h #include
Re: [twsocket] Problem with v6 BCB package
What is your suggestion then? Regards, SubZ I don't like this idea. -- [EMAIL PROTECTED] http://www.overbyte.be - Original Message - From: Fastream Technologies [EMAIL PROTECTED] To: ICS support mailing twsocket@elists.org Sent: Tuesday, February 28, 2006 7:58 AM Subject: Re: [twsocket] Problem with v6 BCB package Francois, I think we should remove the library and types units and embed the code into other units with direct Windows names. OR BETTER, we can rename the functions as ICSGetWindowLong() and ICSHWND. I can do this for you but I want to be assured that my changes will be applied and therefore I would not have to do it every time a new version comes out. Regards, SZ - Original Message - From: Dan [EMAIL PROTECTED] To: ICS support mailing twsocket@elists.org Sent: Monday, February 27, 2006 11:51 PM Subject: Re: [twsocket] Problem with v6 BCB package I didn't think #defines followed namespaces, thought they were always global. Could be wrong... Dan - Original Message - From: Fastream Technologies [EMAIL PROTECTED] To: ICS support mailing twsocket@elists.org Sent: Monday, February 27, 2006 2:19 PM Subject: Re: [twsocket] Problem with v6 BCB package NO wait, you must have got the idea of how to make a namespace from delphi: it is easy and done in all ICS code as it is automatic in Delphi! In Delphi the unit name becomes the namespace name in C++! The problem is in the current situation you -somehow- make the namespace contents public and that causes ambigouity with windows identifiers. We need to either: 1) make the namespace private and calls like OverbyteIcs::getwindowlong OR 2) find a way to remove the namespace from within C++ source code. For example: #include vcl.h #include overbyteicshttpsrv.hpp do NOT use namespace overbyteICS // not sure the syntax here! #include winsock.h Regards, SZ - Original Message - From: Francois Piette [EMAIL PROTECTED] To: ICS support mailing twsocket@elists.org Sent: Monday, February 27, 2006 4:00 PM Subject: Re: [twsocket] Problem with v6 BCB package I have no idea about how to define C++ name space with Delphi code. -- [EMAIL PROTECTED] http://www.overbyte.be - Original Message - From: Fastream Technologies [EMAIL PROTECTED] To: ICS support mailing twsocket@elists.org Sent: Monday, February 27, 2006 2:47 PM Subject: Re: [twsocket] Problem with v6 BCB package No I don't think that would be easy as well... Why don't you use namespaces which are designed for this purpose? You should not include the pascal translation of, use namespace overbyte; instead call functions like Overbyte::getwindowLong(); I understand that you wanted to simply the uses part of the package but this makes it further complicated in the projects. Regards, SZ - Original Message - From: Fastream Technologies [EMAIL PROTECTED] To: ICS support mailing twsocket@elists.org Sent: Monday, February 27, 2006 3:43 PM Subject: Re: [twsocket] Problem with v6 BCB package This won't be as easy as to say: There are 20+ units! What about including a special .h for this purpose that undefs all overbyte defs?? Regards, SZ - Original Message - From: Francois Piette [EMAIL PROTECTED] To: ICS support mailing twsocket@elists.org Sent: Monday, February 27, 2006 3:23 PM Subject: Re: [twsocket] Problem with v6 BCB package #ifdef HWND #undef HWND #endif Put this code (and similar) before the ICS includes. Also try varying the include order between ICS and Windows. -- [EMAIL PROTECTED] http://www.overbyte.be - Original Message - From: Fastream Technologies [EMAIL PROTECTED] To: ICS support mailing twsocket@elists.org Sent: Monday, February 27, 2006 2:04 PM Subject: Re: [twsocket] Problem with v6 BCB package Hello, - Original Message - From: Francois Piette [EMAIL PROTECTED] To: ICS support mailing twsocket@elists.org Sent: Monday, February 27, 2006 12:56 PM Subject: Re: [twsocket] Problem with v6 BCB package I have been able to skip the bug by removing zlibobjs.pas. :-) Now there is a huge design problem: Problems are always huge with you. In OverbyteIcsTypes.pas, you redefined all the types used from windows for compactibality reasons (I believe). However BCB complains (in project with overbyteics package, not in package compilation itself!) there is ambiguity in types and functions such as getwindowlong and HWND and almost all of them! Any idea what can fix it? Maybe add #undef after the units which define them ? Either undefine those symbol from the standards units or from ICS units. Can you give a C++ example? I have code like: #include
Re: [twsocket] Problem with v6 BCB package
Did you get my message below? Anyone has a BCB6 package fix idea for the file below?? Regards, SZ - Original Message - From: Fastream Technologies [EMAIL PROTECTED] To: ICS support mailing twsocket@elists.org Sent: Sunday, February 26, 2006 9:48 AM Subject: [twsocket] Problem with v6 BCB package Hello, Despite all that I have done, the package that I created for BCB6 (http://www.fastream.com/ics/V6.zip) gives linker access violation. Anyone can help? Francois, the last time I asked for your help on this issue, you DENIED for no time and I hope you can just take a look at this package, fix and include in the original zip. 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 -- 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
Re: [twsocket] Problem with v6 BCB package
Despite all that I have done, the package that I created for BCB6 (http://www.fastream.com/ics/V6.zip) gives linker access violation. Anyone can help? Linker access violation is likely a bug in BCB6 itself. I have no idea how to solve that. You should try with BDS2006. The trial version is available now. -- [EMAIL PROTECTED] http://www.overbyte.be - Original Message - From: Fastream Technologies [EMAIL PROTECTED] To: ICS support mailing twsocket@elists.org Sent: Monday, February 27, 2006 9:18 AM Subject: Re: [twsocket] Problem with v6 BCB package Did you get my message below? Anyone has a BCB6 package fix idea for the file below?? Regards, SZ - Original Message - From: Fastream Technologies [EMAIL PROTECTED] To: ICS support mailing twsocket@elists.org Sent: Sunday, February 26, 2006 9:48 AM Subject: [twsocket] Problem with v6 BCB package Hello, Despite all that I have done, the package that I created for BCB6 (http://www.fastream.com/ics/V6.zip) gives linker access violation. Anyone can help? Francois, the last time I asked for your help on this issue, you DENIED for no time and I hope you can just take a look at this package, fix and include in the original zip. 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 -- 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 -- 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
Re: [twsocket] Problem with v6 BCB package
Hello, - Original Message - From: Francois Piette [EMAIL PROTECTED] To: ICS support mailing twsocket@elists.org Sent: Monday, February 27, 2006 10:45 AM Subject: Re: [twsocket] Problem with v6 BCB package Despite all that I have done, the package that I created for BCB6 (http://www.fastream.com/ics/V6.zip) gives linker access violation. Anyone can help? Linker access violation is likely a bug in BCB6 itself. I have no idea how to solve that. You should try with BDS2006. The trial version is available now. I am not planning to spend on BCB until the future of the compiler becomes clearer. And unlikely everybody here will upgrade soon. So I think we need a workaround. Can't you just spend 5 mins to try the package I uploaded? (http://www.fastream.com/ics/V6.zip) 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
Re: [twsocket] Problem with v6 BCB package
I have been able to skip the bug by removing zlibobjs.pas. :-) Now there is a huge design problem: Problems are always huge with you. In OverbyteIcsTypes.pas, you redefined all the types used from windows for compactibality reasons (I believe). However BCB complains (in project with overbyteics package, not in package compilation itself!) there is ambiguity in types and functions such as getwindowlong and HWND and almost all of them! Any idea what can fix it? Maybe add #undef after the units which define them ? Either undefine those symbol from the standards units or from ICS units. -- [EMAIL PROTECTED] http://www.overbyte.be -- 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
Re: [twsocket] Problem with v6 BCB package
Hello, - Original Message - From: Francois Piette [EMAIL PROTECTED] To: ICS support mailing twsocket@elists.org Sent: Monday, February 27, 2006 12:56 PM Subject: Re: [twsocket] Problem with v6 BCB package I have been able to skip the bug by removing zlibobjs.pas. :-) Now there is a huge design problem: Problems are always huge with you. In OverbyteIcsTypes.pas, you redefined all the types used from windows for compactibality reasons (I believe). However BCB complains (in project with overbyteics package, not in package compilation itself!) there is ambiguity in types and functions such as getwindowlong and HWND and almost all of them! Any idea what can fix it? Maybe add #undef after the units which define them ? Either undefine those symbol from the standards units or from ICS units. Can you give a C++ example? I have code like: #include vcl.h #include overbyteicshttpsrv.hpp #include ... ... Where should I enter what? Best 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
Re: [twsocket] Problem with v6 BCB package
This won't be as easy as to say: There are 20+ units! What about including a special .h for this purpose that undefs all overbyte defs?? Regards, SZ - Original Message - From: Francois Piette [EMAIL PROTECTED] To: ICS support mailing twsocket@elists.org Sent: Monday, February 27, 2006 3:23 PM Subject: Re: [twsocket] Problem with v6 BCB package #ifdef HWND #undef HWND #endif Put this code (and similar) before the ICS includes. Also try varying the include order between ICS and Windows. -- [EMAIL PROTECTED] http://www.overbyte.be - Original Message - From: Fastream Technologies [EMAIL PROTECTED] To: ICS support mailing twsocket@elists.org Sent: Monday, February 27, 2006 2:04 PM Subject: Re: [twsocket] Problem with v6 BCB package Hello, - Original Message - From: Francois Piette [EMAIL PROTECTED] To: ICS support mailing twsocket@elists.org Sent: Monday, February 27, 2006 12:56 PM Subject: Re: [twsocket] Problem with v6 BCB package I have been able to skip the bug by removing zlibobjs.pas. :-) Now there is a huge design problem: Problems are always huge with you. In OverbyteIcsTypes.pas, you redefined all the types used from windows for compactibality reasons (I believe). However BCB complains (in project with overbyteics package, not in package compilation itself!) there is ambiguity in types and functions such as getwindowlong and HWND and almost all of them! Any idea what can fix it? Maybe add #undef after the units which define them ? Either undefine those symbol from the standards units or from ICS units. Can you give a C++ example? I have code like: #include vcl.h #include overbyteicshttpsrv.hpp #include ... ... Where should I enter what? Best 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 -- 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 -- 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
Re: [twsocket] Problem with v6 BCB package
No I don't think that would be easy as well... Why don't you use namespaces which are designed for this purpose? You should not include the pascal translation of, use namespace overbyte; instead call functions like Overbyte::getwindowLong(); I understand that you wanted to simply the uses part of the package but this makes it further complicated in the projects. Regards, SZ - Original Message - From: Fastream Technologies [EMAIL PROTECTED] To: ICS support mailing twsocket@elists.org Sent: Monday, February 27, 2006 3:43 PM Subject: Re: [twsocket] Problem with v6 BCB package This won't be as easy as to say: There are 20+ units! What about including a special .h for this purpose that undefs all overbyte defs?? Regards, SZ - Original Message - From: Francois Piette [EMAIL PROTECTED] To: ICS support mailing twsocket@elists.org Sent: Monday, February 27, 2006 3:23 PM Subject: Re: [twsocket] Problem with v6 BCB package #ifdef HWND #undef HWND #endif Put this code (and similar) before the ICS includes. Also try varying the include order between ICS and Windows. -- [EMAIL PROTECTED] http://www.overbyte.be - Original Message - From: Fastream Technologies [EMAIL PROTECTED] To: ICS support mailing twsocket@elists.org Sent: Monday, February 27, 2006 2:04 PM Subject: Re: [twsocket] Problem with v6 BCB package Hello, - Original Message - From: Francois Piette [EMAIL PROTECTED] To: ICS support mailing twsocket@elists.org Sent: Monday, February 27, 2006 12:56 PM Subject: Re: [twsocket] Problem with v6 BCB package I have been able to skip the bug by removing zlibobjs.pas. :-) Now there is a huge design problem: Problems are always huge with you. In OverbyteIcsTypes.pas, you redefined all the types used from windows for compactibality reasons (I believe). However BCB complains (in project with overbyteics package, not in package compilation itself!) there is ambiguity in types and functions such as getwindowlong and HWND and almost all of them! Any idea what can fix it? Maybe add #undef after the units which define them ? Either undefine those symbol from the standards units or from ICS units. Can you give a C++ example? I have code like: #include vcl.h #include overbyteicshttpsrv.hpp #include ... ... Where should I enter what? Best 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 -- 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 -- 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 -- 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
Re: [twsocket] Problem with v6 BCB package
I have no idea about how to define C++ name space with Delphi code. -- [EMAIL PROTECTED] http://www.overbyte.be - Original Message - From: Fastream Technologies [EMAIL PROTECTED] To: ICS support mailing twsocket@elists.org Sent: Monday, February 27, 2006 2:47 PM Subject: Re: [twsocket] Problem with v6 BCB package No I don't think that would be easy as well... Why don't you use namespaces which are designed for this purpose? You should not include the pascal translation of, use namespace overbyte; instead call functions like Overbyte::getwindowLong(); I understand that you wanted to simply the uses part of the package but this makes it further complicated in the projects. Regards, SZ - Original Message - From: Fastream Technologies [EMAIL PROTECTED] To: ICS support mailing twsocket@elists.org Sent: Monday, February 27, 2006 3:43 PM Subject: Re: [twsocket] Problem with v6 BCB package This won't be as easy as to say: There are 20+ units! What about including a special .h for this purpose that undefs all overbyte defs?? Regards, SZ - Original Message - From: Francois Piette [EMAIL PROTECTED] To: ICS support mailing twsocket@elists.org Sent: Monday, February 27, 2006 3:23 PM Subject: Re: [twsocket] Problem with v6 BCB package #ifdef HWND #undef HWND #endif Put this code (and similar) before the ICS includes. Also try varying the include order between ICS and Windows. -- [EMAIL PROTECTED] http://www.overbyte.be - Original Message - From: Fastream Technologies [EMAIL PROTECTED] To: ICS support mailing twsocket@elists.org Sent: Monday, February 27, 2006 2:04 PM Subject: Re: [twsocket] Problem with v6 BCB package Hello, - Original Message - From: Francois Piette [EMAIL PROTECTED] To: ICS support mailing twsocket@elists.org Sent: Monday, February 27, 2006 12:56 PM Subject: Re: [twsocket] Problem with v6 BCB package I have been able to skip the bug by removing zlibobjs.pas. :-) Now there is a huge design problem: Problems are always huge with you. In OverbyteIcsTypes.pas, you redefined all the types used from windows for compactibality reasons (I believe). However BCB complains (in project with overbyteics package, not in package compilation itself!) there is ambiguity in types and functions such as getwindowlong and HWND and almost all of them! Any idea what can fix it? Maybe add #undef after the units which define them ? Either undefine those symbol from the standards units or from ICS units. Can you give a C++ example? I have code like: #include vcl.h #include overbyteicshttpsrv.hpp #include ... ... Where should I enter what? Best 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 -- 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 -- 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 -- 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 -- 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
Re: [twsocket] Problem with v6 BCB package
Well then this is a problem we need to solve for v6 release. ;(( Regards, SZ - Original Message - From: Francois Piette [EMAIL PROTECTED] To: ICS support mailing twsocket@elists.org Sent: Monday, February 27, 2006 4:00 PM Subject: Re: [twsocket] Problem with v6 BCB package I have no idea about how to define C++ name space with Delphi code. -- [EMAIL PROTECTED] http://www.overbyte.be - Original Message - From: Fastream Technologies [EMAIL PROTECTED] To: ICS support mailing twsocket@elists.org Sent: Monday, February 27, 2006 2:47 PM Subject: Re: [twsocket] Problem with v6 BCB package No I don't think that would be easy as well... Why don't you use namespaces which are designed for this purpose? You should not include the pascal translation of, use namespace overbyte; instead call functions like Overbyte::getwindowLong(); I understand that you wanted to simply the uses part of the package but this makes it further complicated in the projects. Regards, SZ - Original Message - From: Fastream Technologies [EMAIL PROTECTED] To: ICS support mailing twsocket@elists.org Sent: Monday, February 27, 2006 3:43 PM Subject: Re: [twsocket] Problem with v6 BCB package This won't be as easy as to say: There are 20+ units! What about including a special .h for this purpose that undefs all overbyte defs?? Regards, SZ - Original Message - From: Francois Piette [EMAIL PROTECTED] To: ICS support mailing twsocket@elists.org Sent: Monday, February 27, 2006 3:23 PM Subject: Re: [twsocket] Problem with v6 BCB package #ifdef HWND #undef HWND #endif Put this code (and similar) before the ICS includes. Also try varying the include order between ICS and Windows. -- [EMAIL PROTECTED] http://www.overbyte.be - Original Message - From: Fastream Technologies [EMAIL PROTECTED] To: ICS support mailing twsocket@elists.org Sent: Monday, February 27, 2006 2:04 PM Subject: Re: [twsocket] Problem with v6 BCB package Hello, - Original Message - From: Francois Piette [EMAIL PROTECTED] To: ICS support mailing twsocket@elists.org Sent: Monday, February 27, 2006 12:56 PM Subject: Re: [twsocket] Problem with v6 BCB package I have been able to skip the bug by removing zlibobjs.pas. :-) Now there is a huge design problem: Problems are always huge with you. In OverbyteIcsTypes.pas, you redefined all the types used from windows for compactibality reasons (I believe). However BCB complains (in project with overbyteics package, not in package compilation itself!) there is ambiguity in types and functions such as getwindowlong and HWND and almost all of them! Any idea what can fix it? Maybe add #undef after the units which define them ? Either undefine those symbol from the standards units or from ICS units. Can you give a C++ example? I have code like: #include vcl.h #include overbyteicshttpsrv.hpp #include ... ... Where should I enter what? Best 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 -- 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 -- 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 -- 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 -- 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 -- 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
Re: [twsocket] Problem with v6 BCB package
NO wait, you must have got the idea of how to make a namespace from delphi: it is easy and done in all ICS code as it is automatic in Delphi! In Delphi the unit name becomes the namespace name in C++! The problem is in the current situation you -somehow- make the namespace contents public and that causes ambigouity with windows identifiers. We need to either: 1) make the namespace private and calls like OverbyteIcs::getwindowlong OR 2) find a way to remove the namespace from within C++ source code. For example: #include vcl.h #include overbyteicshttpsrv.hpp do NOT use namespace overbyteICS // not sure the syntax here! #include winsock.h Regards, SZ - Original Message - From: Francois Piette [EMAIL PROTECTED] To: ICS support mailing twsocket@elists.org Sent: Monday, February 27, 2006 4:00 PM Subject: Re: [twsocket] Problem with v6 BCB package I have no idea about how to define C++ name space with Delphi code. -- [EMAIL PROTECTED] http://www.overbyte.be - Original Message - From: Fastream Technologies [EMAIL PROTECTED] To: ICS support mailing twsocket@elists.org Sent: Monday, February 27, 2006 2:47 PM Subject: Re: [twsocket] Problem with v6 BCB package No I don't think that would be easy as well... Why don't you use namespaces which are designed for this purpose? You should not include the pascal translation of, use namespace overbyte; instead call functions like Overbyte::getwindowLong(); I understand that you wanted to simply the uses part of the package but this makes it further complicated in the projects. Regards, SZ - Original Message - From: Fastream Technologies [EMAIL PROTECTED] To: ICS support mailing twsocket@elists.org Sent: Monday, February 27, 2006 3:43 PM Subject: Re: [twsocket] Problem with v6 BCB package This won't be as easy as to say: There are 20+ units! What about including a special .h for this purpose that undefs all overbyte defs?? Regards, SZ - Original Message - From: Francois Piette [EMAIL PROTECTED] To: ICS support mailing twsocket@elists.org Sent: Monday, February 27, 2006 3:23 PM Subject: Re: [twsocket] Problem with v6 BCB package #ifdef HWND #undef HWND #endif Put this code (and similar) before the ICS includes. Also try varying the include order between ICS and Windows. -- [EMAIL PROTECTED] http://www.overbyte.be - Original Message - From: Fastream Technologies [EMAIL PROTECTED] To: ICS support mailing twsocket@elists.org Sent: Monday, February 27, 2006 2:04 PM Subject: Re: [twsocket] Problem with v6 BCB package Hello, - Original Message - From: Francois Piette [EMAIL PROTECTED] To: ICS support mailing twsocket@elists.org Sent: Monday, February 27, 2006 12:56 PM Subject: Re: [twsocket] Problem with v6 BCB package I have been able to skip the bug by removing zlibobjs.pas. :-) Now there is a huge design problem: Problems are always huge with you. In OverbyteIcsTypes.pas, you redefined all the types used from windows for compactibality reasons (I believe). However BCB complains (in project with overbyteics package, not in package compilation itself!) there is ambiguity in types and functions such as getwindowlong and HWND and almost all of them! Any idea what can fix it? Maybe add #undef after the units which define them ? Either undefine those symbol from the standards units or from ICS units. Can you give a C++ example? I have code like: #include vcl.h #include overbyteicshttpsrv.hpp #include ... ... Where should I enter what? Best 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 -- 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 -- 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 -- 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 -- 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 -- 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
Re: [twsocket] Problem with v6 BCB package
Hello Francois, #undef HWND does not work as it is for the preprocessor but HWND is for the compiler! Any other ideas? Regards, SZ - Original Message - From: Francois Piette [EMAIL PROTECTED] To: ICS support mailing twsocket@elists.org Sent: Monday, February 27, 2006 3:23 PM Subject: Re: [twsocket] Problem with v6 BCB package #ifdef HWND #undef HWND #endif Put this code (and similar) before the ICS includes. Also try varying the include order between ICS and Windows. -- [EMAIL PROTECTED] http://www.overbyte.be - Original Message - From: Fastream Technologies [EMAIL PROTECTED] To: ICS support mailing twsocket@elists.org Sent: Monday, February 27, 2006 2:04 PM Subject: Re: [twsocket] Problem with v6 BCB package Hello, - Original Message - From: Francois Piette [EMAIL PROTECTED] To: ICS support mailing twsocket@elists.org Sent: Monday, February 27, 2006 12:56 PM Subject: Re: [twsocket] Problem with v6 BCB package I have been able to skip the bug by removing zlibobjs.pas. :-) Now there is a huge design problem: Problems are always huge with you. In OverbyteIcsTypes.pas, you redefined all the types used from windows for compactibality reasons (I believe). However BCB complains (in project with overbyteics package, not in package compilation itself!) there is ambiguity in types and functions such as getwindowlong and HWND and almost all of them! Any idea what can fix it? Maybe add #undef after the units which define them ? Either undefine those symbol from the standards units or from ICS units. Can you give a C++ example? I have code like: #include vcl.h #include overbyteicshttpsrv.hpp #include ... ... Where should I enter what? Best 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 -- 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 -- 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
Re: [twsocket] Problem with v6 BCB package
I didn't think #defines followed namespaces, thought they were always global. Could be wrong... Dan - Original Message - From: Fastream Technologies [EMAIL PROTECTED] To: ICS support mailing twsocket@elists.org Sent: Monday, February 27, 2006 2:19 PM Subject: Re: [twsocket] Problem with v6 BCB package NO wait, you must have got the idea of how to make a namespace from delphi: it is easy and done in all ICS code as it is automatic in Delphi! In Delphi the unit name becomes the namespace name in C++! The problem is in the current situation you -somehow- make the namespace contents public and that causes ambigouity with windows identifiers. We need to either: 1) make the namespace private and calls like OverbyteIcs::getwindowlong OR 2) find a way to remove the namespace from within C++ source code. For example: #include vcl.h #include overbyteicshttpsrv.hpp do NOT use namespace overbyteICS // not sure the syntax here! #include winsock.h Regards, SZ - Original Message - From: Francois Piette [EMAIL PROTECTED] To: ICS support mailing twsocket@elists.org Sent: Monday, February 27, 2006 4:00 PM Subject: Re: [twsocket] Problem with v6 BCB package I have no idea about how to define C++ name space with Delphi code. -- [EMAIL PROTECTED] http://www.overbyte.be - Original Message - From: Fastream Technologies [EMAIL PROTECTED] To: ICS support mailing twsocket@elists.org Sent: Monday, February 27, 2006 2:47 PM Subject: Re: [twsocket] Problem with v6 BCB package No I don't think that would be easy as well... Why don't you use namespaces which are designed for this purpose? You should not include the pascal translation of, use namespace overbyte; instead call functions like Overbyte::getwindowLong(); I understand that you wanted to simply the uses part of the package but this makes it further complicated in the projects. Regards, SZ - Original Message - From: Fastream Technologies [EMAIL PROTECTED] To: ICS support mailing twsocket@elists.org Sent: Monday, February 27, 2006 3:43 PM Subject: Re: [twsocket] Problem with v6 BCB package This won't be as easy as to say: There are 20+ units! What about including a special .h for this purpose that undefs all overbyte defs?? Regards, SZ - Original Message - From: Francois Piette [EMAIL PROTECTED] To: ICS support mailing twsocket@elists.org Sent: Monday, February 27, 2006 3:23 PM Subject: Re: [twsocket] Problem with v6 BCB package #ifdef HWND #undef HWND #endif Put this code (and similar) before the ICS includes. Also try varying the include order between ICS and Windows. -- [EMAIL PROTECTED] http://www.overbyte.be - Original Message - From: Fastream Technologies [EMAIL PROTECTED] To: ICS support mailing twsocket@elists.org Sent: Monday, February 27, 2006 2:04 PM Subject: Re: [twsocket] Problem with v6 BCB package Hello, - Original Message - From: Francois Piette [EMAIL PROTECTED] To: ICS support mailing twsocket@elists.org Sent: Monday, February 27, 2006 12:56 PM Subject: Re: [twsocket] Problem with v6 BCB package I have been able to skip the bug by removing zlibobjs.pas. :-) Now there is a huge design problem: Problems are always huge with you. In OverbyteIcsTypes.pas, you redefined all the types used from windows for compactibality reasons (I believe). However BCB complains (in project with overbyteics package, not in package compilation itself!) there is ambiguity in types and functions such as getwindowlong and HWND and almost all of them! Any idea what can fix it? Maybe add #undef after the units which define them ? Either undefine those symbol from the standards units or from ICS units. Can you give a C++ example? I have code like: #include vcl.h #include overbyteicshttpsrv.hpp #include ... ... Where should I enter what? Best 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 -- 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 -- 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 -- 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 -- 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 -- To unsubscribe or change
Re: [twsocket] Problem with v6 BCB package
Francois, I think we should remove the library and types units and embed the code into other units with direct Windows names. OR BETTER, we can rename the functions as ICSGetWindowLong() and ICSHWND. I can do this for you but I want to be assured that my changes will be applied and therefore I would not have to do it every time a new version comes out. Regards, SZ - Original Message - From: Dan [EMAIL PROTECTED] To: ICS support mailing twsocket@elists.org Sent: Monday, February 27, 2006 11:51 PM Subject: Re: [twsocket] Problem with v6 BCB package I didn't think #defines followed namespaces, thought they were always global. Could be wrong... Dan - Original Message - From: Fastream Technologies [EMAIL PROTECTED] To: ICS support mailing twsocket@elists.org Sent: Monday, February 27, 2006 2:19 PM Subject: Re: [twsocket] Problem with v6 BCB package NO wait, you must have got the idea of how to make a namespace from delphi: it is easy and done in all ICS code as it is automatic in Delphi! In Delphi the unit name becomes the namespace name in C++! The problem is in the current situation you -somehow- make the namespace contents public and that causes ambigouity with windows identifiers. We need to either: 1) make the namespace private and calls like OverbyteIcs::getwindowlong OR 2) find a way to remove the namespace from within C++ source code. For example: #include vcl.h #include overbyteicshttpsrv.hpp do NOT use namespace overbyteICS // not sure the syntax here! #include winsock.h Regards, SZ - Original Message - From: Francois Piette [EMAIL PROTECTED] To: ICS support mailing twsocket@elists.org Sent: Monday, February 27, 2006 4:00 PM Subject: Re: [twsocket] Problem with v6 BCB package I have no idea about how to define C++ name space with Delphi code. -- [EMAIL PROTECTED] http://www.overbyte.be - Original Message - From: Fastream Technologies [EMAIL PROTECTED] To: ICS support mailing twsocket@elists.org Sent: Monday, February 27, 2006 2:47 PM Subject: Re: [twsocket] Problem with v6 BCB package No I don't think that would be easy as well... Why don't you use namespaces which are designed for this purpose? You should not include the pascal translation of, use namespace overbyte; instead call functions like Overbyte::getwindowLong(); I understand that you wanted to simply the uses part of the package but this makes it further complicated in the projects. Regards, SZ - Original Message - From: Fastream Technologies [EMAIL PROTECTED] To: ICS support mailing twsocket@elists.org Sent: Monday, February 27, 2006 3:43 PM Subject: Re: [twsocket] Problem with v6 BCB package This won't be as easy as to say: There are 20+ units! What about including a special .h for this purpose that undefs all overbyte defs?? Regards, SZ - Original Message - From: Francois Piette [EMAIL PROTECTED] To: ICS support mailing twsocket@elists.org Sent: Monday, February 27, 2006 3:23 PM Subject: Re: [twsocket] Problem with v6 BCB package #ifdef HWND #undef HWND #endif Put this code (and similar) before the ICS includes. Also try varying the include order between ICS and Windows. -- [EMAIL PROTECTED] http://www.overbyte.be - Original Message - From: Fastream Technologies [EMAIL PROTECTED] To: ICS support mailing twsocket@elists.org Sent: Monday, February 27, 2006 2:04 PM Subject: Re: [twsocket] Problem with v6 BCB package Hello, - Original Message - From: Francois Piette [EMAIL PROTECTED] To: ICS support mailing twsocket@elists.org Sent: Monday, February 27, 2006 12:56 PM Subject: Re: [twsocket] Problem with v6 BCB package I have been able to skip the bug by removing zlibobjs.pas. :-) Now there is a huge design problem: Problems are always huge with you. In OverbyteIcsTypes.pas, you redefined all the types used from windows for compactibality reasons (I believe). However BCB complains (in project with overbyteics package, not in package compilation itself!) there is ambiguity in types and functions such as getwindowlong and HWND and almost all of them! Any idea what can fix it? Maybe add #undef after the units which define them ? Either undefine those symbol from the standards units or from ICS units. Can you give a C++ example? I have code like: #include vcl.h #include overbyteicshttpsrv.hpp #include ... ... Where should I enter what? Best 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 -- To unsubscribe or change your settings for TWSocket mailing list please goto http://www.elists.org/mailman/listinfo/twsocket Visit our website at http
