From mboxrd@z Thu Jan  1 00:00:00 1970
MIME-Version: 1.0
In-Reply-To: <9a90e0026e0caaa0c27978a238e7b605@quintile.net>
References: <9fb1f0189acbe5546193608dae59e08e@isd.dp.ua>
	<9a90e0026e0caaa0c27978a238e7b605@quintile.net>
Date: Thu, 18 Jul 2013 17:30:26 +0300
Message-ID: <CAG3N4d-x5ONcuMq7j+x3TrwkvNpH0acUHK_urZhrdSCS=0_Gag@mail.gmail.com>
From: Yaroslav <yarikos@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Content-Type: text/plain; charset=UTF-8
Subject: Re: [9fans] mallocz in APE
Topicbox-Message-UUID: 6c7ad15c-ead8-11e9-9d60-3106f5b1d025

>> Replacing _MALLOCZ back with mallocz within APE realm seems to me a
>> better option to consider.
>
> I don't think this is better. APE generally tries very hard to be compliant
> to the spirit of ANSI (or POSIX with _POSIX_EXTENSION defined), this
> includes not poluting the namespace with plan9isms where possible.
>
> Having said this what about setmalloctag() getcallerpc(), etc etc.

It is internal to the libraries and is not exposed to the APE apps, right?