Tim Peters <tim.one@comcast.net> writes: >> Sure, but that's only an issue if you are allocating resources in one >> runtime lib and deallocating in another AFAIK. There's nothing >> beyond memory allocation going on here, and the type object in >> question has a custom deallocator which goes to the same runtime that >> allocated it. > > See my later msg -- returning memory to a heap it wasn't obtained from is > fatal enough. I think that's exactly what I said. > The object memory itself is in question here, not memory > allocated *by* the object. I think that's also exactly what I thought. -- Dave Abrahams Boost Consulting www.boost-consulting.com
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4