Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watnot!watmath!clyde!cbatt!ihnp4!vax135!cjp
From: cjp@vax135.UUCP
Newsgroups: comp.sys.amiga
Subject: My.lib
Message-ID: <1795@vax135.UUCP>
Date: Wed, 11-Mar-87 04:24:13 EST
Article-I.D.: vax135.1795
Posted: Wed Mar 11 04:24:13 1987
Date-Received: Thu, 12-Mar-87 18:38:15 EST
References: <8703101916.AA09847@cory.Berkeley.EDU>
Reply-To: cjp@vax135.UUCP (Charles Poirier)
Organization: AT&T Bell Labs, Holmdel, NJ
Lines: 15

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?

	(I have no relationship to Manx Software Systems, Inc.) --
	Charles Poirier