Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!mailrus!uwmcsd1!ig!agate!ucbvax!mips.csc.ti.COM!peterson From: peterson@mips.csc.ti.COM (Bob Peterson) Newsgroups: comp.lang.modula2 Subject: Re: A Free M2 Library Message-ID: <8809051828.AA23929@mips> Date: 5 Sep 88 18:28:29 GMT References: <8809021249.AA04797@klaus.olsen.uucp> Sender: daemon@ucbvax.BERKELEY.EDU Reply-To: Info-Modula2 Distribution List Organization: TI Computer Science Center, Dallas Lines: 48 In article <8809021249.AA04797@klaus.olsen.uucp> you write: >We have an ~80 module M2 library which we are going to release to the >public domain within the next few weeks. I have several questions >which will help me get the library ready for release. Please respond >to me directly (I will acknowledge receipt). If you would like to >know a bit about the library before answering these questions, I have >included a short description at the end of this note. > > 1. Is anyone interested in the library? Are you interested in being > a beta test site? Yes, there is interest in the library, but I'm not in a good position to be a beta test site. > 2. How would you like the library distributed? Source only? > Separate binary and source distributions? All the modules > in one directory? We have an added complication that the > library must be preprocessed before it is compiled. This doubles > the number of sources files. (You need to keep both copies around > if you want to debug the library.) Do you want our test programs? Source only is preferable, in my opinion. How the files are organized isn't that important, since I'll probably rearrange them anyway. I gather there is a problem with supplying the preprocessor? Otherwise you wouldn't need to provide the preprocessed version of the source? Yes, I most certainly want the test programs! Not only can they be used to ensure correct transmission, but to do regression testing when I make changes. Also, when recompiling or porting the code, your tests can help find any problems. > 3. We have quite an extensive manual. The text formatter we use > is Latex. Will this be a problem? (Note: the definition modules > are well commented so the need for a manual is not as great as > with other libraries.) LaTeX is not a problem for me, and I even have a way of producing ASCII from the .dvi output file. The latter is useful for those sites without LaTeX, e.g., personal computer users. >Thanx for any responses, >Rob Nagler >olsen!nagler@uunet.uu.net >Olsen & Associates >Seefeldstrasse 23 THANK YOU!! -- Hardcopy and Electronic Addresses: Office: Bob Peterson Compuserve: 70235,326 NB 2nd Floor CSC Aisle C3 P.O. Box 861686 Usenet: peterson@csc.ti.com Plano, Tx USA 75086 (214) 995-6080 (work) or (214) 596-3720 (ans. machine)