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

Reply via email to