home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!richsun!richsun.cpg.trs.reuters.com!pej
- From: pej@richsun.cpg.trs.reuters.com (Paul Jatkowski)
- Newsgroups: comp.lang.eiffel
- Subject: Re: Eiffel on UNIX
- Message-ID: <3536@richsun.cpg.trs.reuter.com>
- Date: 30 Jul 92 19:22:45 GMT
- References: <5496@m1.cs.man.ac.uk>
- Sender: news@richsun.cpg.trs.reuter.com
- Reply-To: pej@richsun.cpg.trs.reuters.com (Paul Jatkowski)
- Organization: REUTERS Client Site Systems
- Lines: 15
-
- In article <5496@m1.cs.man.ac.uk>, ian (Ian Cottam) writes:
- |> Will ISE Eiffel 3 still use the UNIX sbrk call for some memory
- |> management? Given that many library functions use malloc
- |> (even fprintf on the SUNs I belive), should not sbrk be reserved
- |> for the implementors of (alternative) mallocs?
-
- In the current release you can #define XENIX in _internal.c and
- recompile the run time
- library. Malloc makes a number of assumptions that are not true a
- program does an sbrk
- after it's first malloc. The core files are *interesting*
-
- Paul Jatkowski
- Reuters
-
-