Object introspection

[pradeepta]

Is there a mechanism in C++ or any library which will give typeinfo
about the members of a struct/class. Something like Boost::type_traits
which will expose type_info of the members too.

[mlimber]

pr*******@gmail.com wrote:

Is there a mechanism in C++ or any library which will give typeinfo
about the members of a struct/class. Something like Boost::type_traits
which will expose type_info of the members too.

Only if you expose the typeinfo of the members by making the data
members accessible (i.e., public for everyone, protected for
subclasses, or open to friendships) or by publishing one or more member
functions to make it available to the user of the class. Generally
speaking, exposing such information would violate the principle of
encapsulation, which rightly tries to hide implementation details (cf.
http://www.parashift.com/c++-faq-lit....html#faq-7.4).

Cheers! --M

[pradeepta]

Let me explain furthur, I want to write a smart structure copy template
function which will inspect the argument (struct/class template) and do
a member-wise assignment across the two arguments.

<class T> const T& smart_copy(const T& arg1, T& arg2)

using template metaprogramming (Eg using BOOST_PP* like functions)

[red floyd]

pr*******@gmail.com wrote:

Let me explain furthur, I want to write a smart structure copy template
function which will inspect the argument (struct/class template) and do
a member-wise assignment across the two arguments.

<class T> const T& smart_copy(const T& arg1, T& arg2)

using template metaprogramming (Eg using BOOST_PP* like functions)

What's wrong with using T's operator=(), which knows how to do it properly?

e.g.

template<class T>
const T& smart_copy(const T& arg1, T& arg2)
{
return arg2 = arg1;
}

[pradeepta]

I am trying to use templating to do lot of boilerplate implementations
from an existing codebase (in C) using a c++ compiler (gcc). One way
would be for me to write a correct "=" operation for each struct/class
and use it, but then it is tedious and error-prone (and I am a lazy
person).
Secondly I would like to write generic functions which can introspect
the template parameters and do "stuff" with them. If boost::type_traits
goes so far as to give me some properties of my type, why not give me
the names/types etc of members of that type?
Just curious...