"Emil Dotchevski" <emil@revergestudios.com> wrote in message news:AANLkTin=9rdwNqHQZRAPj9=9YngdTD0mX7zQ8S1LmhQm@mail.gmail.com...
On Sat, Oct 9, 2010 at 12:38 PM, Daniel Walker <daniel.j.walker@gmail.com> wrote:
Finally, there have been suggestions to alter boost::function's exception safety guarantee directly through either policies or constructor options.
We used to have an Allocator parameter to the boost::function template and it was removed (just in time for this change to also be reflected in C++0x) to reduce coupling. Adding any policies to boost::function would undo all of the benefits of that change.
What (de)coupling (and the related benefits) are you referring to? The ABI compatibility/stability and safe cross .DLL/.so passing arguments also used for the justification of the hardcoded dynamic deleter in shared_ptr or something else? -- "What Huxley teaches is that in the age of advanced technology, spiritual devastation is more likely to come from an enemy with a smiling face than from one whose countenance exudes suspicion and hate." Neil Postman