From: mhw@minster.york.ac.uk (Mark H. Wilkinson)
To: sam-fans@hawkwind.utcs.toronto.edu (sam mailing list)
Subject: sam's memory allocator
Date: Fri, 7 Apr 1995 06:14:02 -0400 [thread overview]
Message-ID: <swordfish.797246527@minster.york.ac.uk> (raw)
In the SP&E paper about sam it's mentioned that sam uses a custom memory
allocator which allocates strings in a garbage-compacted heap. The version
which is released these days uses just malloc() and realloc(). What was
the reason for throwing the custom allocator away?
-Mark.
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Mark H. Wilkinson <mhw@minster.york.ac.uk> : Research student in user
University of York, England : interface management systems
next reply other threads:[~1995-04-07 9:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1995-04-07 10:14 Mark H. Wilkinson [this message]
1995-04-07 15:40 rob
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=swordfish.797246527@minster.york.ac.uk \
--to=mhw@minster.york.ac.uk \
--cc=sam-fans@hawkwind.utcs.toronto.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).