Ive searched in boost a typeid wrapper like the one Andrei Alexandrescu uses in his book (Modern C++ Design), but didnt found any, except one in the python library. It seemed very much what Im searching, so I'm wondering why it is in the python library. I think it is a very useful feature outside python library either. So Im asking if it shouldnt be a general class in the boost library, instead of being a feature to be used by the python library only? Thanks in advance, -- Felipe Magno de Almeida UIN: 2113442 email: felipe.almeida@ic unicamp br, felipe.m.almeida@gmail com I am a C, modern C++, MFC, ODBC, Windows Services, MAPI developer from synergy, and Computer Science student from State University of Campinas(UNICAMP). To know more about: Unicamp: http://www.ic.unicamp.br Synergy: http://www.synergy.com.br current work: http://www.mintercept.com
Felipe Magno de Almeida wrote:
Ive searched in boost a typeid wrapper like the one Andrei Alexandrescu uses in his book (Modern C++ Design), but didnt found any, except one in the python library. It seemed very much what Im searching, so I'm wondering why it is in the python library. I think it is a very useful feature outside python library either. So Im asking if it shouldnt be a general class in the boost library, instead of being a feature to be used by the python library only?
I think Jody Hagins was working recently to move some of the typeid machinery out of Python into detail. I'm not sure if this includes what you are talking about, or what progress has been made, but you might want to search for recent messages on the subject. Jonathan
Felipe Magno de Almeida wrote:
I think it is a very useful feature outside python library either. So Im asking if it shouldnt be a general class in the boost library, instead of being a feature to be used by the python library only?
FWIW, boost::fsm currently also has its own typei_info wrapper and I'm aware of at least another proposed lib that would benefit of such a thing. So the need is definitely there, even for a boost::detail-only implementation. Regards, -- Andreas Huber When replying by private email, please remove the words spam and trap from the address shown in the header.
Andreas Huber wrote:
Felipe Magno de Almeida wrote:
I think it is a very useful feature outside python library either. So Im asking if it shouldnt be a general class in the boost library, instead of being a feature to be used by the python library only?
FWIW, boost::fsm currently also has its own typei_info wrapper and I'm aware of at least another proposed lib that would benefit of such a thing. So the need is definitely there, even for a boost::detail-only implementation.
IIRC, serialization library also has it's own extended type info facilities. Jeff Flinn
On Sun, 20 Feb 2005 14:14:57 -0300 Felipe Magno de Almeida <felipe.almeida@ic.unicamp.br> wrote:
Ive searched in boost a typeid wrapper like the one Andrei Alexandrescu uses in his book (Modern C++ Design), but didnt found any, except one in the python library. It seemed very much what Im searching, so I'm wondering why it is in the python library. I think it is a very useful feature outside python library either. So Im asking if it shouldnt be a general class in the boost library, instead of being a feature to be used by the python library only?
I have done most of the work to move the python one out "on its own." Unfortunately, I ran into a snag. Specifically, I can not get all the tests to build correctly using bjam. I seem to have everything working for unix, using makefiles, but can not get it to work with bjam. I think this is essential, especially to run all the tests on non-unix platforms. <advertisement> I would be happy to resume the effort if I can get some specific involvement from someone who can help me get everything running with Boost.Build. </advertisement>
Jody Hagins <jody-boost-011304@atdesk.com> writes:
On Sun, 20 Feb 2005 14:14:57 -0300 Felipe Magno de Almeida <felipe.almeida@ic.unicamp.br> wrote:
Ive searched in boost a typeid wrapper like the one Andrei Alexandrescu uses in his book (Modern C++ Design), but didnt found any, except one in the python library. It seemed very much what Im searching, so I'm wondering why it is in the python library. I think it is a very useful feature outside python library either. So Im asking if it shouldnt be a general class in the boost library, instead of being a feature to be used by the python library only?
I have done most of the work to move the python one out "on its own." Unfortunately, I ran into a snag. Specifically, I can not get all the tests to build correctly using bjam. I seem to have everything working for unix, using makefiles, but can not get it to work with bjam. I think this is essential, especially to run all the tests on non-unix platforms.
<advertisement> I would be happy to resume the effort if I can get some specific involvement from someone who can help me get everything running with Boost.Build. </advertisement>
What problems are you having? It might be best to take this to the jamboost list. -- Dave Abrahams Boost Consulting www.boost-consulting.com
Did you by any chance take a look at extended_typeinfo and void_cast from the serialization library? Robert Ramey Felipe Magno de Almeida wrote:
Ive searched in boost a typeid wrapper like the one Andrei Alexandrescu uses in his book (Modern C++ Design), but didnt found any, except one in the python library. It seemed very much what Im searching, so I'm wondering why it is in the python library. I think it is a very useful feature outside python library either. So Im asking if it shouldnt be a general class in the boost library, instead of being a feature to be used by the python library only?
Thanks in advance,
participants (7)
-
Andreas Huber -
David Abrahams -
Felipe Magno de Almeida -
Jeff Flinn -
Jody Hagins -
Jonathan Turkanis -
Robert Ramey