|
Boost : |
From: Vladimir Prus (ghost_at_[hidden])
Date: 2002-09-12 07:11:49
Bohdan wrote:
> "Vladimir Prus" <ghost_at_[hidden]> wrote in message
> news:3D805A49.4020308_at_cs.msu.su...
>
>>You'd need support from compiler, I guess.
>>
>
>
> Sure it would be better to have support from compiler, but ... :(
> The best thing i can imagine now is well known 'describe' function
> (possibly wrapped
> by some macros). It can be internal or external (for class).
Yes. BTW, what do you think about const correctness issues of 'describe'
that is also considered in this thread.
> The other idea ( from Konstantin Knizhnik ) is to traverse
> debug info, but i do not like it too much. It is too complicated, besides
> all it
> is not compiler independent.
I don't like it either.
> Yet another way can be c++ parser (spirit lib?) ... i'm going too far?
> :)
There's gcc-xml (http://www.gccxml.org) which can emit some type
information.
However, you'd need to integrate your tool with the build process. Some
folks will have no problem with it, others might object.
- Volodya
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk