jmaag@a.cs.okstate.edu (John Maag) (09/14/88)
To whom it may concern:
I am writing a shell that will assist students in the software
development process. What the shell will do is automate the make
process. It will automatically keep track of files and their
dependent files. It will also remake an object file and execute it.
If the object program bombs off, sdb will be interfaced automatically
and an editor will be executed for the file containing the function
that is on top of the stack (the function that caused the abend).
It will also do several other things like global change (a change to
multiple files with an edit on each one to confirm the changes and
an interface to sccs so that source files are backed up automatically.
If anyone knows of something similar, please let me know.
John Maag internet: (jmaag@a.cs.okstate.edu)
UUCP: ({cbosgd, ihnp4, rutgers}!okstate!jmaag
--
John Maagphil@aimt.UUCP (Phil Gustafson) (09/15/88)
In article <3906@okstate.UUCP>, jmaag@a.cs.okstate.edu (John Maag) writes: > > To whom it may concern: > > I am writing a shell that will assist students in the software > development process. What the shell will do is automate the make > process. It will automatically [do lots of stuff] > > John Maag May I suggest caution? There's a fundamental rule of automation that says "Everything automatically done _for_ you simultaneously does something unpredicted and usually unpleasant _to_ you." -- Phil Gustafson, Graphics/UN*X Consultant net address above 1550 Martin Ave, San Jose, Ca 95126