Path: utzoo!mnetor!uunet!lll-winken!lll-tis!oodis01!uplherc!utah-gr!utah-cs!peeler.utah.edu!u-lchoqu From: u-lchoqu%peeler.utah.edu.uucp@utah-cs.UUCP (Lee Choquette) Newsgroups: comp.sys.mac.programmer Subject: Re: Source code library idea! Message-ID: <5478@utah-cs.UUCP> Date: 9 May 88 18:00:43 GMT References: <730024@hpcilzb.HP.COM> <9561@agate.BERKELEY.EDU> Sender: news@utah-cs.UUCP Reply-To: u-lchoqu%sunset.utah.edu@utah-cs.UUCP (Lee Choquette) Organization: University of Utah CS Dept Lines: 23 Summary: Simtel a willing site; how to store the sources? The Simtel moderator, Robert Thum, likes the idea of creating a source subdirectory. As for how the sources should be stored, in article <9561@agate.BERKELEY.EDU> jmm@bartleby.berkeley.edu (James Moore) writes: I like the idea of a source code library, but why do you want to have it in Stuffed/Binned format? If you just want to look at the code, it would be much easier not to have to download it to a Mac. I would also assume that most people have much faster/better printers available from their Unix accounts. True, but how should multiple files be packaged? Many programs consists of several source files. A proliferation of TOPS-20 subdirectories would be a nightmare for everyone involved, and shell archives could be unpacked only by people running Unix. Once we resolve this question, I have a few megabytes of Mac source code collected from various sources (including comp.sources.mac) with which to start the archive. -- Lee Choquette u-lchoqu@ug.utah.edu University of Utah Computer Center utah-gr!utah-ug!u-lchoqu MEB 3440 Choquette@UTAHCCA.Bitnet Salt Lake City, UT 84112-1180 (801) 581-8504