From: John Maddock (john_at_[hidden])
Date: 2003-12-21 06:08:57
> I don't think it would be a bug for Boost.Python. Any DLL that
> doesn't pass resources outside its boundaries can be built with a
> static runtime IIUC.
True, but there aren't many of those, if python can do it (I didn't alter
anything there you'll be pleased to know), then serious kudos to you.
> > This issue should be fixed in cvs now (I've also re-enabled
> > install-stage for date_time lib on NT, as this does actually work
> > now).
> This seems like a slightly drastic step to take without some
> discussion first.
Not that drastic - most of the dll targets already had that constraint on
them, there were two that I changed:
thread - throws exceptions from the library - that counts as sharing
resources IMO, as the client deletes the string that gets thrown inside the
runtime_error object (and in any case I know from bitter experience that
with Borland's compiler you really do have to insure that the code doing the
catching shares the same EH runtime as the code throwing, or your app
date_time - one API (get_month_map_ptr) returns a shared_ptr, I'm pretty
sure that shared_ptr's internal use-count memory management will get tripped
up here unless caller and callee share the same runtime.
Boost-Build list run by bdawes at acm.org, david.abrahams at rcn.com, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk