1This is a much modified version of the public domain spread sheet sc, 2posted several years ago by Mark Weiser as vc, originally by James Gosling. 3 4Changes since my last version (5.1) are detailed at great length :-) 5in CHANGES (sequent!rgb (Robert Bond)). 6 7When you get it built, try "sc tutorial.sc" for a simple introduction 8to the basic commands. 9 10A new input parser program (psc) has been included. This program 11formats ascii files for use in the spread sheet. If you don't have 12getopts, there is a public domain version by Henry Spencer hidden away 13in the VMS_NOTES file. 14 15I have modified the makefile to make it easy for you to call the 16program what you want (I saw at least five different names in 17correspondence and on the net). Just change "name=sc" and "NAME=SC" to 18"name=myfavoritename" and "NAME=MYFAVORITENAME" and try "make 19myfavoritename". 20 21Similarly, you can make the documentation with "make myfavoritename.man". 22"make install" will make and install the code in EXDIR. The 23installation steps and documentation all key off of the name. The 24makefile even changes the name in the nroffable man page. If you don't 25have nroff, you will have to change sc.man yourself. 26 27This release has been tested against a Sequent S81 running DYNIX 3.0.14 28(BSD 4.2) and an ICM-3216 with system V.3. The ICM has a National Semi 2932016. Just check the makefile for the system flags. I have heard 30reports of lots of other machines that work. If you have problems with 31lex.c, and don't care about arrow keys, define SIMPLE (-DSIMPLE in the 32makefile). SIMPLE causes the arrow keys to not be used. 33 34Guidelines for Hackers: 35 36If you want to send changes you have made to SC, please feel free to do 37so. If they work :-) and seem worthwhile, I'll put them in. Please 38refrain from wholesale "style" or "cleanup" changes. It is easy to add 39your changes but it makes it hard to merge in the next guy's stuff if 40he used the release as a base. Leave my $Revision: identifiers alone- 41they help me track what you used as a base. If you check the code into 42rcs, delete the "$"s on the Revison lines before you do. 43 44You may not like 4 space indenting and curly braces on the "if" line, 45but your code will look like that before it leaves my hands so you may 46as well abide by the style in the code when you make your changes. I 47have also been known to break things trying to make them look "right". 48If you do string functions, please, PLEASE pay attention to null 49pointers, use xmalloc and xfree, and xfree those arguments. And 50don't forget to document your changes in both help.c and sc.doc. 51 52Disclaimer: 53 54Starting 4/4/90: (I will be maintaining Sc for a while at least, 55 Robert Bond has been very busy lately) 56Sc is not a product of Grauel Enterprises, Inc. It is supplied as 57is with no warranty, express or implied, as a service to Usenet readers. 58It is not copyrighted, either. Have at it. 59 60 Jeff Buhrt 61 Grauel Enterprises, Inc. 62 {pur-phy (aka: newton.physics.purdue.edu), sequent}!sawmill!buhrt 63