Path: utzoo!utgpu!watmath!clyde!att!pacbell!ames!think!bloom-beacon!apple!desnoyer
From: desnoyer@Apple.COM (Peter Desnoyers)
Newsgroups: comp.lang.c
Subject: Re: inkey$, noecho, and other impossibles
Message-ID: <23757@apple.Apple.COM>
Date: 11 Jan 89 17:55:12 GMT
References: <19@xenlink.UUCP> <225800106@uxe.cso.uiuc.edu> <310@twwells.uucp> <84629@sun.uucp> <15396@mimsy.UUCP> <9338@smoke.BRL.MIL>
Organization: Apple Computer Inc, Cupertino, CA
Lines: 11

In article <9338@smoke.BRL.MIL> gwyn@brl.arpa (Doug Gwyn (VLD/VMB) <gwyn>) writes:
>In article <15396@mimsy.UUCP> chris@mimsy.UUCP (Chris Torek) writes:
>>Possibly.  In fact, malloc() might be one (`too machine dependent').
>
I don't think malloc is a problem on most reasonable machines. Brk and
sbrk, however, are bad gotchas. If you can allocate memory in any way,
you can probably allocate blocks in a way that allows you to construct
malloc. However, you may not be able to paste the allocated blocks
together to get sbrk semantics.

				Peter Desnoyers