> On 09/24/11 08:49 AM, Malcolm McLean wrote:
>> On Sep 23, 9:02 pm, jacob navia<ja...@spamsink.net> wrote:
>>> You allocate stuff with gc_malloc() and never free it. That is all
>>> there is. I do not see why that is no longer 'C'.
>> gc_malloc() can't be implemented in standard C, and requires intimate
>> knowledge of the architecture to sweep for orphaned memory blocks and
>> add them to the free list. That's enught o classify it as an extension
>> rather than simply as a new function. There's also the practical
>> reason that memory allocation is very fundamental, it changes the way
>> most programs are written.
> I don't see why people get so hung up in garbage collection. The
> compiler I mainly use has shipped with a collector since the 90s and it
> is still a standard C compiler. If I want to use the collector, all I
> have to do is link it with my standard C executable. Does the act of
> linking a garbage collector somehow make my code non-standard?
Well, that is gcc. Gcc can do whatever they want, the problem
is when lcc-win does the same :-)