Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!ub!acsu.buffalo.edu From: cloos@acsu.buffalo.edu (James H. Cloos) Newsgroups: comp.sys.handhelds Subject: Libraries and versions Message-ID: <68505@eerie.acsu.Buffalo.EDU> Date: 3 Apr 91 01:40:38 GMT Sender: news@acsu.Buffalo.EDU Organization: State University of New York @ Buffalo Lines: 47 Nntp-Posting-Host: lictor.acsu.buffalo.edu I was thinking the otehr day about how I want to include copyright messages, etc. in my libraries. Given the number that are out there, I would like to avoid any possibility of name conflicts--at least with the version and copyright stuff. I'm looking at the following format for each of the commands to assure continuity and no conflicts: (Below, `name' refers to a libraries (possibly abbreviated) name and `number' to its (decimal) id number. Also, I'll use `@' to refer to \169, the copyright symbol.) @name [see next] @number paints a copyright screen, incl author's name, whether copyrighted or pd, whether freeware, shareware, or commercialware. This shows up as Cnumber in the menu. VERSname [see next] VERSnumber returns a version number to the stack. Should be design- ed so that a program that uses the routines in this lib call use this to confirm whether it'll work. This shouldn't add too much to the size of the libs. (I'll bet this will even be a concern when 3-d memory devices are perfected and the handhelds have 64 (or maybe 256 or 4K) address and data lines--word-addressed at that; no more of this byte-addressing nonsense (IMHO).) If there is a very large profusion of libraries out there, it would be nice to be able to have on-line mention of who wrote it; obviously copyrighted stuff in general and shareware/commercialware stuff in specific NEED this info. Further assuming that these libraries will not be static projects, allowing programs that use them to confirm that the needed version of the lib is there is helpful. (NB: the code /<< VERS1500 4.52 SAME \>> not only tests to see if the version is 4.52, but also tests whether the library is ATTACHed in the first place.) I thought I'd put this out onto the net to elicit responces. Please post all replies so that a resounding discussion can take place! ;^) Seriously, though, all replies are welcome! Happy (system (sh!)) Programming! -JimC -- James H. Cloos, Jr. Phone: +1 716 673-1250 cloos@ACSU.Buffalo.EDU Snail: PersonalZipCode: 14048-0772, USA cloos@ub.UUCP Quote: <>