1

Topic: On what platforms type_info:: op == does not compare a line?

In libstdc ++ and libc ++ type_info:: operator == it is implemented through : #if _PLATFORM_SUPPORTS_UNIQUE_TYPEINFO bool operator == (const type_info& __ rhs) const {return __ mangled_name == __ rhs. __ mangled_name;} #else bool operator == (const type_info& __ rhs) const {return __ mangled_name == __ rhs. __ mangled_name || strcmp (__ mangled_name, __ rhs. __ mangled_name) == 0;} #endif I.e. there are any platforms where or is not present.so generally, or is guaranteed that at loading.so, dynamic  unites data RTTI. What it for platforms? (If to whom the karma on SO is necessary - double the answer here)

2

Re: On what platforms type_info:: op == does not compare a line?

Well and why did not make ? http://www.macs.hw.ac.uk/~hwloidl/hacks … 3/typeinfo

//Determine whether typeinfo names for the same type are merged (in which//case comparison can just compare pointers) or not (in which case strings//must be compared), and whether comparison is to be implemented inline or//not. We used to do inline pointer comparison by default if weak symbols//are available, but even with weak symbols sometimes names are not merged//when objects are loaded with RTLD_LOCAL, so now we always use strcmp by//default. For ABI compatibility, we do the strcmp inline if weak symbols//are available, and out-of-line if not. Out-of-line pointer comparison//is used where the object files are to be portable to multiple systems,//some of which may not be able to use pointer comparison, but the//particular system for which libstdc ++ is being built can use pointer//comparison; in particular for most ARM EABI systems, where the ABI//specifies out-of-line comparison. The compiler's target configuration//can override the defaults by defining __ GXX_TYPEINFO_EQUALITY_INLINE to//1 or 0 to indicate whether or not comparison is inline, and//__ GXX_MERGED_TYPEINFO_NAMES to 1 or 0 to indicate whether or not pointer//comparison can be used. #ifndef __ GXX_MERGED_TYPEINFO_NAMES//By default, typeinfo names are not merged. #define __ GXX_MERGED_TYPEINFO_NAMES 0 #endif

3

Re: On what platforms type_info:: op == does not compare a line?

Hello, reversecode, you wrote: R> well and why did not make ? R> http://www.macs.hw.ac.uk/~hwloidl/hacks … 3/typeinfo R>

R>... The comment for 20 lines... R>

well on what platforms?

4

Re: On what platforms type_info:: op == does not compare a line?

In the quoted 20 lines it has been clearly told, I  transfer about Google  will not be

5

Re: On what platforms type_info:: op == does not compare a line?

Hi, reversecode, you here wrote: R> in the quoted 20 lines it has been clearly told, I  transfer about Google  will not be With all the heart the brother. At once it is felt that came on Russian forum, already shed a few tears.