Return to the
comp.compilers page.
Search the
comp.compilers archives again.
| From: | mwotton@cse.unsw.edu.au (Mark Alexander Wotton) |
| Newsgroups: | comp.compilers |
| Date: | 13 Jul 2003 23:54:01 -0400 |
| Organization: | Mare's Nest Collective |
| References: | 03-05-211 03-06-015 03-06-054 03-06-057 03-06-078 03-07-005 03-07-048 |
| Keywords: | GC |
| Posted-Date: | 13 Jul 2003 23:54:00 EDT |
On 4 Jul 2003 00:06:26 -0400, Basile STARYNKEVITCH posted:
> >> mwotton@cse.unsw.edu.au (Mark Alexander Wotton) wrote
> >>> Either that, or only released when all references to it have
> >>> passed out of scope. This is how many modern garbage-collected
> >>> language implementations work.
>
> Modern GC are usually *not* reference-counters based! But some crude
> language implementations do happen to have poor garbage collectors,
> sometimes only reference-counting based (which works poorly for
> reference cycles and costs a lot).
Sorry, I was being imprecise. From ten thousand feet up, the idea of garbage
collection is to deallocate memory that is no longer referenced, ie
out of scope. Whether you do it immediately (reference counting) or later is
an implementation issue.
mrak
Return to the
comp.compilers page.
Search the
comp.compilers archives again.