Based on my (limited) understanding: * Inside the same linked executable (an EXE, DLL, etc..), you can only have a single implementation of something, such as operator new, operator delete, etc..
* Inside different linked executables that are dynamically linked (or statically linked using shared libraries), you can have one implementation per shared library For instance: MyCoolGame.exe can use its own custom implementation of operator new/operater delete WebKit.dll can use another custom implementation that is different from MyCoolGame.exe UberGraphicsLibrary.dll can use yet another custom implementation that is different from both WebKit.dll and MyCoolGame.exe However, WebCore.lib and JavaScriptCore.lib, which are linked into WebKit.dll, have to use the same implementation, since even though they are different static libraries, they are linked into a single linkable executable. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Darin Adler Sent: Wednesday, June 04, 2008 2:01 PM To: Paul Pedriana Cc: WebKit-Dev Subject: Re: [webkit-dev] WebKit memory management? On Jun 4, 2008, at 10:57 AM, Paul Pedriana wrote: > As I mentioned in a previous response, this unfortunately doesn't > work because all operator new is directed to FastMalloc, not just > WebKit's usage of operator new. Operator new is global in a linkage > unit. Did you try it, or is that just something you know without testing? I understand the principle, but I haven't seen the problem in practice on any platform. If the problem is a real practical issue, do you have a suggested fix? Would you be willing to make a patch to show what it would look like? -- Darin _______________________________________________ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev _______________________________________________ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
