-----Original Message----- From: boost-bounces@lists.boost.org [mailto:boost-bounces@lists.boost.org] On Behalf Of Jeremy Pack
I agree. It would be very compiler dependent to have the library find arbitrary classes in a linked library and determine their methods. What I was thinking of is a bit simpler. It would require a reflected class to have it's reflected methods declared as such. It would be a bit similar to the Boost.Python syntax, except that it would, like Boost.Extension, require only one library entry point and it would need to add some stuff for type safety, without inducing a lot of runtime overhead.
I see. Perhaps I should get more familiar with Boost.Python. Would have loved to go to Boost Con. /me shakes fist at new passport requirements Sohail