-=> Quoting George White to John Dumas <=-
 GW> You wrote to Carey Bloodworth:
 
 JD> CB> you aren't supposed to know how it does it.  (In fact, it can, and
 JD> This contrary to every other part of the language.
 GW> ?????
 GW> It is consistant with every other part of the standard library in my
 GW> experience. There is _nothing_ anywhere that defines that a standard
 GW> library function has to be written in a certain way, just that it has
 GW> to take certain parameters, perform a specified operation and
 GW> return/set specified results and return/set specified error conditions
 GW> values. 
 Because of the very nature of C the functions are just not used like
 constructing a sentence as in some other languages.  
 The inputs type,length,limets, as well as, the same for the output and the
 way the functions operate are in my library reference books as well as 
 a lot of examples of how these functions are written as in "Craft of C"
 and other books and information to an extent that I ( in my "limeted" 
 observations of other languages) have not yet seen matched.  
 What I an basically saying is C is highly documented and explained 
 compared to other languages and the inscrutability and non-excess 
 of the memory alocation proccess is not consistant with the rest of 
 the language. 
 
 explained 
... Even a broken clock is correct twice a day ( W.F.B.)
--- Blue Wave/DOS v2.20 [NR]
---------------