BTW, these are resolved by playing with directories' order in Project Options...
Thanks anyway for reading. On Sat, Oct 17, 2009 at 4:14 PM, Fastream Technologies <ga...@fastream.com>wrote: > Ok forcing ICS to use integer instead of Byte did not work either. But why > does this error occur? How could the compiler find System.Byte and Byte > ambigous? What could be the source of this??! > > > On Sat, Oct 17, 2009 at 2:09 PM, Fastream Technologies <ga...@fastream.com > > wrote: > >> Ok my very simple question about Delphi and ICS: How do we enforce a type >> for a const? For example in C++, >> static const int dummy = 1; is the way to force a static const >> integer called dummy with a variable value of "1". If we can force ICS to >> use integer for all const in SSL units, my problem will be resolved. And >> probably others' too?? >> >> Regards, >> >> SZ >> >> >> On Sat, Oct 17, 2009 at 12:52 PM, Fastream Technologies < >> ga...@fastream.com> wrote: >> >>> Hello, >>> >>> I see in ...libeay.pas for example: >>> >>> const >>> SSL_SESS_CACHE_NO_AUTO_CLEAR = $0080; >>> >>> which translates in BCB2010 in header as, >>> >>> static const Byte SSL_SESS_CACHE_NO_AUTO_CLEAR = 0x80; >>> which is confusing for most projects as there are usually lots of "Byte" >>> defined. Giving, >>> >>> [BCC32 Error] Overbyteicsssleay.hpp(703): E2015 Ambiguity between 'Byte' >>> and 'System::Byte' >>> >>> errors. Isn't there a way to force the DCC compiler not to produce Byte >>> for const and instead for example WORD or int ? >>> >>> Best Regards, >>> >>> SZ >>> >> >> -- 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
