[Webkit-unassigned] [Bug 27029] Allow custom memory allocation control in the whole JSCore

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Thu Jul 9 09:29:05 PDT 2009


https://bugs.webkit.org/show_bug.cgi?id=27029





--- Comment #1 from Darin Adler <darin at apple.com>  2009-07-09 09:29:04 PDT ---
(In reply to comment #0)
> The problem was in the case of Noncopyable, if I inherited Noncopyable from
> FastAllocBase it occured multiple new definitions and build errors (ambigous
> 'new' using). 
> Further problems come up with e.g. JSCell, because it's also inherited from
> Noncopyable and overrides operator new because of using GC, so it's also cause
> conflicts.

I think we can create two different Noncopyable. One for most uses that does
include FastAllocBase, and the other for the few cases that customize operator
new.

And if there are few enough cases of the non-FastAllocBase Noncopyable, then we
could just do those by hand, rather than using a base class. But I'd prefer to
use a base class if it's more than, say, 3 or 4 classes overall.

Maybe NoncopyableCustomAllocated as the name for the new Noncopyable variant?
And put it in Noncopyable.h?

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.



More information about the webkit-unassigned mailing list