Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!clyde.concordia.ca!uunet!cs.utexas.edu!tut.cis.ohio-state.edu!att!cbnewsc!gregg
From: gregg@cbnewsc.ATT.COM (gregg.g.wonderly)
Newsgroups: comp.sys.amiga
Subject: Re: Lattice C 5.04 bug
Message-ID: <12147@cbnewsc.ATT.COM>
Date: 11 Dec 89 16:03:56 GMT
References: <828@wet.UUCP>
Organization: AT&T Bell Laboratories
Lines: 31

From article <828@wet.UUCP>, by mcw@wet.UUCP (Martin Warnett):
> There appears to be a bug in the chdir() function in Lattice C 5.04.
> When I run my program from the CLI everything works fine. However when
> the same program ran from the WB, it ran fine and terminated but the
> system locked up and I had to reboot. I couldn't even click on a disk
> icon.

Which brings me to my favorite gripe.  Why do people insist on implementing
compatibility libraries from the lowest level?  It seems really rediculous
to try and invent new bugs in software.  My favorite is the sleep()
implementation in C-Kermit.  Instead of 

sleep(n)
	unsigned n;
{
	Delay (60*n);
}

the code was written with huge amounts of StartIO/WaitIO and other such
nonsense.  This is really why the Exec functions were written.  Once
these routines are written and debugged (most were long ago), there are
no more worries.

Please folks use the highest level of interface, not the lowest, even though
you know how to do it.  I look much more highly on those that do it the
easiest way rather than the "trickest" way.  Remember, the code has to
work right before being faster makes a difference...

-- 
-----
gregg.g.wonderly@att.com   (AT&T bell laboratories)