... as you can verify by this:
http://msdn.microsoft.com/en-us/library/ms235460.aspx
So, like I said, if you design the EXE and the DLL to use the same MSVCRT DLL, then they will use the same heap and you can call new/delete with impunity.
If you don't, well, you are sad panda.
- Casey
http://msdn.microsoft.com/en-us/library/ms235460.aspx
So, like I said, if you design the EXE and the DLL to use the same MSVCRT DLL, then they will use the same heap and you can call new/delete with impunity.
If you don't, well, you are sad panda.
- Casey
It's not on youtube yet, no spoilers please!
EDIT: Anyway, hahhahah!
EDIT: Anyway, hahhahah!
Edited by Livet Ersomen Strøm
on
yeah, sorry for the "non-question" : D
It was one of those things where the second I saw the msdn docs (and this post from Raymond Chen), the whole idea instantly became completely obvious.
It was one of those things where the second I saw the msdn docs (and this post from Raymond Chen), the whole idea instantly became completely obvious.
To me that explanation was shocking.
During my C course nobody talked about the C Runtime Library.
As a consequence i always thought that new, malloc and variants were exactly the same as virtualalloc.
I understand now that i rely heavily on the CRT, understand what it is and what it does for me.
Thank you for that clarification!
Bert
During my C course nobody talked about the C Runtime Library.
As a consequence i always thought that new, malloc and variants were exactly the same as virtualalloc.
I understand now that i rely heavily on the CRT, understand what it is and what it does for me.
Thank you for that clarification!
Bert