Xref: utzoo comp.unix.programmer:2161 comp.unix.shell:2530
Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!samsung!dali.cs.montana.edu!caen!zaphod.mps.ohio-state.edu!pacific.mps.ohio-state.edu!linac!midway!uwvax!margay.cs.wisc.edu!dws
From: dws@margay.cs.wisc.edu (DaviD W. Sanderson)
Newsgroups: comp.unix.programmer,comp.unix.shell
Subject: is there a job control library?
Message-ID: <1991Jun27.235850.11100@spool.cs.wisc.edu>
Date: 27 Jun 91 23:58:50 GMT
Sender: news@spool.cs.wisc.edu (The News)
Organization: U of Wisconsin CS Dept
Lines: 23
Originator: dws@margay.cs.wisc.edu

I am curious whether anyone has implemented (or even designed) a generic
job control library that would be suitable for adding job control to
a shell that does not already have it.

	There could be a consistent approach to job control across all
	the shells that used the library, and a central place to make
	fixes and updates.

	Alternative mechanisms for job control (e.g. using sxts) could
	be supported through the same programming interface to the
	shell by using an appropriate version of the library.

Is a generic library interface to job control for shells feasable?
Or are "jobs" necessarily so intimately bound up with the rest of the
innards of a shell that it would be prohibitive to abstract out job
control?
-- 
       ___
      / __\  U N S H I N E	           DaviD W. Sanderson
     |  |  | I N E			    dws@cs.wisc.edu
_____|  |  |_____  ________
\      / \   |__/ /////__	Fusion Powered Locomotives Made to Order
 \____/   \__|_/  \\\\\______	 (TARDIS model available at extra cost)