Path: utzoo!attcan!telly!lethe!torsqnt!news-server.csri.toronto.edu!bonnie.concordia.ca!uunet!maverick.ksu.ksu.edu!phobos.cis.ksu.edu!set
From: set@phobos.cis.ksu.edu (Steve E Tietze )
Newsgroups: comp.sys.amiga.programmer
Subject: C lib.
Message-ID: <1991Feb13.174940.11484@maverick.ksu.ksu.edu>
Date: 13 Feb 91 17:49:40 GMT
Sender: news@maverick.ksu.ksu.edu (The News Guru)
Organization: Kansas State University, Dept. of Computing and Information Sciences
Lines: 48

Im posting this for someone.




Here you go Peter.  

steve t.



Reply to: cmp8163@sys.uea.ac.uk
Newsgroups: comp.sys.amiga.programmer
Distribution: comp
Subject: CCLib.library problems (REPOST - Please reply)
Summary: CCLib has errors
Keywords: cclib,shared library, C standard library

I have asked this question before, but I'd really like to get
some people to look into the following problem :

The cclib.library, posted as shareware, allows C programmers to
use the standard C library functions (printf, puts, fopen, seek, etc.)
as a shared amiga library. This is VERY useful if multiple tasks 
need access, because it used to be the case that a duplication of
those functions were in memory all the time. 
I found some SERIOUS problems with it, though. For example,
if a fopen() or fputs() fails, because of, for example, a disk
being full, the CCLIB DOES *NOT* check the internal Amiga error
return codes !! So even if you carefully check whether the write 
succeeded or not, the error in cclib causes the machine to crash !
This problem makes people reject the library, which is a shame,
since the idea is really good. The problems can be duplicated
easily if you try to write to the following filename :
FOO:foo.foo. A standard requester will come up 
"Insert volume FOO...". Click on CANCEL, and the machine crashes.
Why ?
If someone knows the whereabouts of the author, could he please let
me know ?
Thanks,


Peter Vlietstra
cmp8163@sys.uea.ac.uk <------- please use this reply address
University of East Anglia
Norwich
England.