Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!sdd.hp.com!spool.mu.edu!munnari.oz.au!brolga!uqcspe!cs.uq.oz.au!grue
From: grue@cs.uq.oz.au (Frobozz)
Newsgroups: comp.sys.handhelds
Subject: Re: Libraries and versions
Message-ID: <580@uqcspe.cs.uq.oz.au>
Date: 4 Apr 91 12:14:15 GMT
Article-I.D.: uqcspe.580
References: <68505@eerie.acsu.Buffalo.EDU> <11542@jarthur.Claremont.EDU>
Sender: news@cs.uq.oz.au
Reply-To: grue@cs.uq.oz.au
Lines: 39

In <11542@jarthur.Claremont.EDU> sburke@jarthur.Claremont.EDU (Scott Burke) writes:


>With respect to copyright notices and name conflicts:

[details of the ABOUT... scheme deleted]

>I would urge against TOO MANY different sub-programs in the Library sub-menu;
>instead, we have gone with a single ABOUT... key (an idea I stole from the 
>Macintosh standard interface of an About Box).

>Sound reasonable?

I like the idea with one reservation: if you ever upgrade a library to
include extra functionality (which is quite likely to happen given the
history of computing's love of creeping featurism) how do you indicate
that the library is the later/earlier version?

For a single purpose library that is a self-contained package, I cannot
see any problems (since there isn't any decent method of accessing the
internals of the library).  For a utility library, this would cause more
headaches.

I suppose you could always try to use the command and fail if it doesn't
exist ;-)




        						Pauli
seeya

Paul Dale               | Internet/CSnet:            grue@cs.uq.oz.au
Dept of Computer Science| Bitnet:       grue%cs.uq.oz.au@uunet.uu.net
Uni of Qld              | JANET:           grue%cs.uq.oz.au@uk.ac.ukc
Australia, 4072         | EAN:                          grue@cs.uq.oz
                        | UUCP:           uunet!munnari!cs.uq.oz!grue
f4e6g4Qh4++             | JUNET:                     grue@cs.uq.oz.au
--