Re: Historical Implementations to Garbage Collectors

Hans-Peter Diettrich <DrDiettrich1@aol.com>
Thu, 22 May 2014 13:37:15 +0200

          From comp.compilers

Related articles
[6 earlier articles]
Re: Historical Implementations to Garbage Collectors gneuner2@comcast.net (George Neuner) (2014-05-06)
Re: Historical Implementations to Garbage Collectors acolvin@efunct.com (mac) (2014-05-06)
Re: Historical Implementations to Garbage Collectors genew@telus.net (Gene Wirchenko) (2014-05-06)
Re: Historical Implementations to Garbage Collectors gneuner2@comcast.net (George Neuner) (2014-05-07)
Re: Historical Implementations to Garbage Collectors kaz@kylheku.com (Kaz Kylheku) (2014-05-07)
Re: Historical Implementations to Garbage Collectors robin51@dodo.com.au (Robin Vowels) (2014-05-21)
Re: Historical Implementations to Garbage Collectors DrDiettrich1@aol.com (Hans-Peter Diettrich) (2014-05-22)
| List of all articles for this month |

From: Hans-Peter Diettrich <DrDiettrich1@aol.com>
Newsgroups: comp.compilers
Date: Thu, 22 May 2014 13:37:15 +0200
Organization: Compilers Central
References: 14-05-001 14-05-009 14-05-012 14-05-017 14-05-021 14-05-025
Keywords: storage
Posted-Date: 22 May 2014 23:00:07 EDT

Robin Vowels schrieb:
> From: "George Neuner" <gneuner2@comcast.net>


>> Pointer:length pairs permit multiple use of substrings, but don't
>> permit constructing a new string from arbitrary pieces of existing
>> ones. The tree representation can permit completely arbitrary
>> substring sharing.
>
> The overheads of that would be intolerable. The address-length
> pair is simple to use, can be passed easily as an argument
> (and returned easily from a function), and there is -- essentially --
> no overhead until the dynamic string space gets used up,
> after which garbage collection is necessary.


Just a note:


I found tree representations for strings in editors, implementing
unlimited Undo. Obviously such applications are not related to small
memory nor to garbage collection.


DoDi


Post a followup to this message

Return to the comp.compilers page.
Search the comp.compilers archives again.