[C++-sig] Re: Presenting a Python embedding tutorial for Boost.Python

David Abrahams dave at boost-consulting.com
Wed Dec 11 14:15:55 CET 2002

Dirk Gerrits <dirk at gerrits.homeip.net> writes:

> Mike Rovner wrote:
>> "Dirk Gerrits" <dirk at gerrits.homeip.net> wrote in message
>> news:at59bp$skj$1 at main.gmane.org...
>>>Furthermore, there should be a way to set/query the currently active
>>>interpreter. Member functions like this:
>>>     bool is_current() const;
>>>     void make_current();
>>>were the first things that came to mind.
>> How about being consistent with scope() interface?
>> Creating new interpreter changes current, but one can create
>> objects to keep and use another.
>> Just my 2c.
> I like the idea of making the new instance the current interpeter. I'm
> just not so sure what the destructor of the current interpreter should
> do. Perhaps the most current interpreter still in scope should be
> looked up in an interpreter registry? Or would it make sense to have
> no current interpreter at all?
> I just don't know enough about creating and using sub-interpreters at
> this point.

I'd like to help make this decision, but I'm having trouble imagining
what the consequences or usefulness of having multiple interpreters
is.  I didn't read that whole article I pointed you at ;-/.  Can you
give me the quick skinny on this?


                       David Abrahams
   dave at boost-consulting.com * http://www.boost-consulting.com
Boost support, enhancements, training, and commercial distribution

More information about the Cplusplus-sig mailing list