70087 - pull string allocation out of XPCOM

Status: RESOLVED WONTFIX

(Core :: XPCOM, defect, P1)

Description

[Scott Collins]

string allocation needs to be in the string library (for standalone), and
callers, in general, need cleanup.  String allocation needs to be settable.  In
discussion, the proposal that seemed best is by configuration, a site-specific
file provides allocators which the string library retrieves through known global
functions.  The allocators would be static objects at the function level, within
the global getters.  This makes order of initialization defined, and allows
clients to simply provide their own allocators at build time.  XPCOM is the
first such client, and the moved allocators will exactly match their XPCOM
compatibility requirements.

Comment 1

[Scott Collins]

re-targeting milestones, starting from a clean slate

Comment 2

[Scott Collins]

giving up ancient string bugs to the new string owner.  jag, you'll want to sort
through these and see which ones still apply and go with or against the
direction in which you intend strings evolve