Path: utzoo!attcan!utgpu!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!rutgers!uwvax!umn-d-ub!nic.MR.NET!shamash!rosevax!ems!pwcs!stag!daemon
From: to_stdnet@stag.UUCP
Newsgroups: comp.sys.atari.st
Subject: Re: Looking for an Evangelist
Message-ID: <681@stag.UUCP>
Date: 22 Dec 88 21:15:18 GMT
Sender: daemon@stag.UUCP
Lines: 27

From: dynasoft!john@stag.UUCP (John Stanley)

[peter@sugar.uu.net (Peter da Silva) writes...]

> TOS, of course, doesn't let you do this... its memory management has a fatal
> bug that forces everyone to roll their own. but I'll wager that if you free
> something twice in a complex 'C' program and let it run long enough it'll
> crash.

  You'd loose the wager if the C program used the dLibs (public domain) C
librarys for the ST....  You can free memory blocks at random locations
from here to doomsday and the machine will fall apart from old age before
the program will crash...  dLibs has been extensively tested by some of
the best crazies I know of. :^)  I'd safely say that anyone developing in
C on the ST who is not using this library is probably working far harder
than they need to.

  (When/where can I collect on your wager?  :^)

--
PS:  Please note that my Reply-To address gets munged by the gateway
I'm currently using for news access so you can't just <r>eply to this
article and have your message get to me.  Please use the address below.

---
John Stanley (dynasoft!john@stag.UUCP)
Software Consultant / Dynasoft Systems