Click here to see the number of accesses to this library.
file readme for overview of sequent file screen for is a virtual terminal manager for people with regular terminals (folks , too poor to buy Sun's for every programmer). It lets you have multiple , independant sessions, each on it's own full size screen. It's very , useful, seemingly bug free, and we use it here quite a lot. by Patrick Wolfe <pwolfe@KAI.COM> Nov 1987 file prolog for implements "standard" (Clocksin & Mellish) Prolog, including a , compiler to translate prolog to Warren Abstract Machine (WAM) , byte codes. # To receive the files try: send prolog from sequent by Bob Beck, Sequent 12/23/87 file team for was motivated by requests for single user mode privileges for , benchmarking purposes. Its predecessor was a shell script from Southern , Methodist University. by Russell Ruby - email@example.com - February 1988 - Oregon State University file schedule for The Schedule Package is an environment for the transportable , implementation of parallel algorithms in a Fortran setting. , By this we mean that a user's code is virtually identical for , each machine. The Schedule Package has been designed to aid , a programmer familiar with a Fortran programming environment , to implement a parallel algorithm in a manner that will lend , itself to transporting the resulting program across a wide , variety of parallel machines. The package is designed to allow , existing Fortran subroutines to be called through Schedule, , without modification, thereby permitting users access to a wide , body of existing library software in a parallel setting. by Jack Dongarra and Dan Sorensen , Mathematics and Computer Science Division , Argonne National Laboratory , June 1987 file parmacs for This is an implementation of the shared-memory constructs from ANL , Parmacs (Lusk, Overbeek, et.al.) in C++. It illustrates how C++ can , be used to build parallel programming constructs, and numerous , advantages over the ANL M4 implementation. These advantages include , extensibility, strong type checking, ease of readability and use, and , use of an object-oriented lanuage. by Bob Beck, Sequent Computer Systems, 9/88