Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!rutgers!iuvax!uxc.cso.uiuc.edu!tank!eecae!cps3xx!usenet
From: usenet@cps3xx.UUCP (Usenet file owner)
Newsgroups: comp.sys.amiga.tech
Subject: Re: Minix, Unix on the Amiga, and flames on AmigaDOS braindamage...
Message-ID: <4148@cps3xx.UUCP>
Date: 14 Aug 89 02:14:14 GMT
References: <1610@uw-entropy.ms.washington.edu> <195@VAX1.CC.UAKRON.EDU> <7570@cbmvax.UUCP> <4107@sugar.hackercorp.com>
Reply-To: porkka@frith.UUCP (Joe Porkka)
Organization: Michigan State University
Lines: 29

In article <4107@sugar.hackercorp.com> karl@sugar.hackercorp.com (Karl Lehenbauer) writes:
>In article <7570@cbmvax.UUCP>, jesup@cbmvax.UUCP (Randell Jesup) writes:
>> I consider any program on ANY os that doesn't
>> free what it allocates (memory, file locks, whatever) to be at best poorly
>> written.
>
>Careful, Randall, I think you've been using your Amiga too long.  
>
>There is no reason a program should have to free its memory if the operating 
>system does it.  Programs written for such an OS cannot be considered


Even worse, even in UNIX, is programs that fail to check if
they are out on memory.

Most UNIX programs *do not* ever check this. UNIX programmers assume
a blissful computer with plenty enough VM to get by.

Well, we have a Sun386i here. With several messydos windows open, it
does run out of memory (im not sure exactly what the problem is, but 
it has something to do with the fact that DOS emultions run in real
memory and is not subject to VM).
When this happens, most thing will segmentation-fault, since they
don't check for NULLs returned by malloc.


Of course no Amiga programmer ever forgets to check such things :-)

REAL NAME: Joe Porkka   jap@frith.cl.msu.edu