D Kernel Development

[Leandro Lucarella]

Jesse Robinson, el 12 de noviembre a las 21:02 me escribiste:
> > Sean Kelly:
> > > Right.  I think Walter meant that "new" would use the GC for allocation, so stubbing out gc_malloc() entirely will break "new".  I suggested replacing the GC with a non-collecting allocator, something like the malloc/free-based stub in Druntime.  Using this, "new" will work but you'll have to call "delete" to release the memory.<
> > 
> > It can be useful to have a single compilation flag that replaces the GC with the stub, removes the larger GC from the binary, and totally disallows the usage of array resizes, array concatenations, associative arrays and closures.
> > 
> > Bye,
> > bearophile
> 
> Such as flag would be very useful in cases like this. Basically, have a switch to turn D in a leaner language for OS / system development.

I think LDC already have this flag, it doesn't change the GC
implementation and I haven't tested it either though :)

-noruntime   - Do not allow code that generates implicit runtime calls

-- 
Leandro Lucarella (AKA luca)                     http://llucax.com.ar/
----------------------------------------------------------------------
GPG Key: 5F5A8D05 (F8CD F9A7 BF00 5431 4145  104C 949E BFB6 5F5A 8D05)
----------------------------------------------------------------------
Just because you're paranoid, don't mean they're not after you.