Talk:Run-time type information
Merging with datatype
- I vote to keep the entry separate. I believe that the theme allows for a more comprehensive text, and if it is merged, it would probably remain as it is.
- oppose Nereocystis 14:54, 7 October 2005 (UTC)
I too oppose
- Oppose too, it'd be hidden if it were merged, makes more sense on its own. EAi 16:38, 27 October 2005 (UTC)
- dfgdfg ddg dfgd gdfg dfgdfg dg dfgdf g gdfg dgdg dfgdf —R. Koot 20:12, 25 November 2005 (UTC)
Provided code example won't compile with g++ (4.0.2). Compilation produces "source type is not polymorphic" error. Adding virtual destructor to the base class solves the problem.--Iwasz 21:59, 21 March 2006 (UTC)
Currently, the article states:
- In programming, RTTI [...] means keeping information about an object's data type in memory at runtime
Isn't it more correct to say:
- In programming, RTTI [...] means keeping information about an entity's data type in memory at runtime
Why is this identified as a C++ thing?
Delphi has had RTTI since the very beginning, and it's integrated into the language and used throughout the runtime, unlike C++ where it was bolted on after the fact and is a special option that has to be enabled. —Preceding unsigned comment added by 126.96.36.199 (talk) 21:14, 22 April 2009 (UTC)
I concur. Run-time type information (in the non-Proper Noun sense) is a feature that is available in all reflective languages, of which there are MANY. The term "Reflection" is virtually identical in meaning to RTTI but is much more accepted academically. Either this article should be merged with Reflection (computer programming), or it should document the other languages such as Delphi and D Programming Language that also refer specifically to "RTTI" as a proper noun, or perhaps this page should just be expunged as it is currently just a piece of technical information specific to C++, which makes it completely irrelevant to encyclopedia readers. --188.8.131.52 (talk) 11:53, 20 August 2009 (UTC)