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

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Tue Jul 7 08:10:10 PDT 2009


           Summary: Allow custom memory allocation control in the whole
           Product: WebKit
           Version: 528+ (Nightly build)
          Platform: PC
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: Normal
          Priority: P2
         Component: JavaScriptCore
        AssignedTo: webkit-unassigned at lists.webkit.org
        ReportedBy: hzoltan at inf.u-szeged.hu

I got a request from Eric to prepare a whole patch for JSCore instead of
sending single class inheritance patches.

I have some problems and we need to clear up FastAllocBase inheritance

It's easy to inherit from a single classes which instantiated by 'new' and
don't have super classes. It's clear.

At multiple inheritance case the policy was to go up as far as I can in the
inheritance tree and inherite the superclass from FastAllocBase (bug #20422). 
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
What should be the policy? Remove that Noncopyable inheritances which causes
conflicts or push FastAllocBase as far as I can in the inheritance tree? (In
the second case there'll be many more inherites from FastAllocBase)



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