Leandro Lucarella wrote:
Andrei Alexandrescu, el 20 de enero a las 19:13 me escribiste:
Leandro Lucarella wrote:
Andrei Alexandrescu, el 20 de enero a las 17:39 me escribiste:
Leandro Lucarella wrote:
Danny Wilson, el 20 de enero a las 16:44 me escribiste:
On Wed, 20 Jan 2010 14:18:52 +0100, Leandro Lucarella
<llu...@gmail.com> wrote:
Again? RC is *not* -nogc, is -anothergc. And reference counting won't do
the trick unless you add a backing GC to free cycles. What I mean about
-nogc is *no* GC, is "please, mr compiler, give me an error when a GC
facility is used".
I guess a custom object.d which static asserts as soon as a GC
facility is used would do that trick?
I don't see how you can do that, all the code calling the GC is in the
runtime AFAIK.
Things can be arranged such that all calls originate in object.d.
But that would mean moving a lot of funcionality from the runtime to
object.d, which doesn't seems to be practical.
Well someone needs to do it to assess practicality and other consequences.
Having half the runtime in object.d is not practical, come on! object.d
was supposed to be the file defining the Object class, that's it!
It doesn't have to contain the runtime, only the entry points to it.
Andrei
