Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watnot!watmath!clyde!cbatt!ucbvax!CORY.BERKELEY.EDU!dillon
From: dillon@CORY.BERKELEY.EDU.UUCP
Newsgroups: comp.sys.amiga
Subject: Re: My.lib
Message-ID: <8703111909.AA17863@cory.Berkeley.EDU>
Date: Wed, 11-Mar-87 14:09:17 EST
Article-I.D.: cory.8703111909.AA17863
Posted: Wed Mar 11 14:09:17 1987
Date-Received: Thu, 12-Mar-87 23:46:22 EST
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: University of California at Berkeley
Lines: 26


>Matt, not to belittle your efforts in developing my.lib, but could you
>supply us with a little sales pitch as to why Manx users (which
>includes, I gather, yourself now) should prefer my.lib functions over
>the Manx-supplied string and stdio functions?  Because my gut reaction
>to using a pet library to do standard kinds of things is kind of
>"ugh".  I know how the standard functions work; what (apart from being
>a library better-organized than Lattice's original) is better about
>my.lib that justifies learning a slightly different set of functions?
>
>By the way, Matt, re your comment where you did something slick to
>avoid including some exec .h file: isn't that largely irrelevant when
>one can use a Manx precompiled header +h file?

	Two things.

    (A) MY.LIB's xstdio() library uses the same argument order as 
    read/write/etc... not the backward argument order stdio uses.  E.G
    specifically xgets(fi, buf, maxbytes) and stdio's fgets(buf, maxbytes, fp)

    (B) MY.LIB provides an asyncronous for writes.

	It is not a matter of learning stdio.... I know exactly how stdio
works.  I used it for years.... I hated every moment.

					-Matt