NetNews Usenet Archive 1992 #30/NN_1992_30.iso/spool/comp/lang/cplus/18253

Text File | 1992-12-21 | 1.6 KB | 35 lines

Newsgroups: comp.lang.c++
Path: sparky!uunet!munnari.oz.au!metro!extro.ucc.su.OZ.AU!maxtal
From: [e-mail] (John MAX Skaller)
Subject: Re: Operator "new" - how to catch array-allocation?
Message-ID: <[e-mail]>
Sender: [e-mail]
Nntp-Posting-Host: extro.ucc.su.oz.au
Organization: MAXTAL P/L C/- University Computing Centre, Sydney
References: <[e-mail]> <[e-mail]>
Date: Sun, 20 Dec 1992 12:25:27 GMT
Lines: 22

In article <[e-mail]> [e-mail] (Morten Sabroe Mortensen) writes:
>The reason I raised this in the first place is, I'm about to build my own
>special-purpose-heap-manager, -the way I would like it to work, is to attach
>"something" to a given class, and then the result should be, that all dynamic
>allocation involving that class should be managed - the way you allocate
>should be independent of how heap-management is controlled - controlled by
>the normal general-purpose manager or a special-purpose manager!
>As I see it, -now-, I can't get this independency - except when allocating
>single instances of the used class! Right?
>

    It is not currently possible to overload operator new[],
if only because there is no such operator. There is a proposal
before the committee to allow this, and I dont believe there are any
in-principle objections to it.


--
;----------------------------------------------------------------------
        JOHN (MAX) SKALLER,         [e-mail]
    Maxtal Pty Ltd, 6 MacKay St ASHFIELD, NSW 2131, AUSTRALIA
;--------------- SCIENTIFIC AND ENGINEERING SOFTWARE ------------------