Comments on: Visual Studio 6 vs 2005 allocators

By: Celvin

Celvin — Mon, 24 Mar 2008 18:09:43 +0000

Well, it might be true that sometimes you don’t have a choice if you’re integrating 3rd party components – but to be true, components written like this are VERY poorly designed and you should probably think twice about integrating those into your projects. Everybody ought to know that memory allocation and freeing have to be done using the same runtime. This is not even limited to VC6 vs. 2005, but can happen in different runtime versions for a given compiler, too.

By: smithbob

smithbob — Wed, 30 Jan 2008 16:05:40 +0000

“Allocating objects in a DLL and requesting user code to delete them (or vice versa) is misconception however…” …

yes but some times you do have the choice because you use/integrate a third party component …

By: cb

cb — Sun, 27 Jan 2008 13:19:55 +0000

At least we didn’t have to recompile our kernel to fix that

By: JulienW

JulienW — Sun, 27 Jan 2008 12:59:36 +0000

All this is Windows’ fault.

By: YR

YR — Sat, 26 Jan 2008 15:06:52 +0000

Allocating objects in a DLL and requesting user code to delete them (or vice versa) is misconception however…

By: cb

cb — Sat, 26 Jan 2008 01:27:49 +0000

thanks bob =)
you’re a guru anyway =)

By: smithbob

smithbob — Fri, 25 Jan 2008 19:52:26 +0000

“… a custom one that can take a previously allocated buffer” … this custm allocator is called a placement new. I now we are not a advanced C blog but it has to be said …

and no, I am not the guru who help cb …..