Allocatoin policy in Phobos - Was: Vote for std.process

deadalnix deadalnix at gmail.com
Fri Apr 12 12:43:25 PDT 2013


On Friday, 12 April 2013 at 17:41:59 UTC, Walter Bright wrote:
> On 4/12/2013 7:05 AM, Manu wrote:
>> I'll start doing it myself, but I also suggest it be made a 
>> policy, and
>> carefully considered when considering acceptance of ANY new 
>> module. That way,
>> new code that suffers the unpredictable/"surprise!" allocation 
>> problems won't be
>> introduced.
>
> I would also expect that Phobos modules that know the lifetimes 
> of their allocated data use malloc/free rather than the gc.
>

Why not use GC.free ? malloc is invisible for the GC, so nothing 
GCed can be stored there safely.


More information about the Digitalmars-d mailing list