rtti

I know by TMS Aurelius that we can use the "new" 2010 attributes feature to serialize database table fields into object properties at run-time, for example, and I am not an expert on this deep object oriented schema, so I look into the TMS source code and could not understand how to implement it myself, not for DB, not for XML. So I've looked for all Google's results on Delphi Attributes and all that people post are declaration examples and then stops before even showing their examples in action. Then where are the real world examples of how can we project, declare, code and USE those juiced

Considering such an enumeration : type TTypeOfData = ( [XmlName('ABC')] todABC, [XmlName('DEF')] todDEF, [XmlName('GHI')] todGHI ); Where XmlName is a custom attribute used to define the serialization string for members of this enumeration. How can I explore the attributes attached to each member of this enumeration ? Attributes associated with elements in enumerations are not currently stored in Win32 RTTI data in the executable. RTTI is already responsible for a fair increase in the size of executables, so some lines had to be drawn somewhere. Attributes in Delphi Win32 are supported on

If I want to use std::any I can use it with RTTI switched off. The following example compiles and runs as expected also with -fno-rtti with gcc. int main() { std::any x; x=9.9; std::cout << std::any_cast<double>(x) << std::endl; } But how std::any stores the type information? As I see, if I call std::any_cast with the "wrong" type I got std::bad_any_cast exception as expected. How is that realized or is this maybe only a gcc feature? I found that boost::any did also not need RTTI, but I found also not how that is solved. Does boost::any need RTTI? . Digging into the STL header itself gives me

What, if any, c++ constructs are there for listing the ancestors of a class at runtime? Basically, I have a class which stores a pointer to any object, including possibly a primitive type (somewhat like boost::any , which I don't want to use because I need to retain ownership of my objects). Internally, this pointer is a void* , but the goal of this class is to wrap the void* with runtime type-safety. The assignment operator is templated, so at assignment time I take the typeid() of the incoming pointer and store it. Then when I cast back later, I can check the typeid() of the cast type

I'm using gcc's -fno-rtti flag to compile my C++ without runtime type information. Assuming I'm not using dynamic_cast<> or typeid() , is there anything that could lead me to later problems? Since your question is specific to GCC you should consult carefully the documentation for the version you are using. The documentation for GCC 4.5.2 says the following. Which from my reading would indicate that if you avoid dynamic_cast and typeid, you should be ok. That said, I have no personal experience with -fno-rtti. Perhaps you might like to elaborate on why you are using -fno-rtti. -fno-rtti Disable