Path: utzoo!news-server.csri.toronto.edu!cs.utexas.edu!uunet!lpi.liant.com!hts
From: hts@lpi.liant.com (Tom Sandlin)
Newsgroups: comp.lang.fortran
Subject: Re: VMS vs. Unix Fortran
Message-ID: <1991Mar5.162559.14224@lpi.liant.com>
Date: 5 Mar 91 16:25:59 GMT
References: <592@siswat.UUCP> <1991Feb27.170224.20411@lpi.liant.com> <1991Mar1.103001.1@dev8h.mdcbbs.com>
Organization: Language Processors Inc., Framingham MA
Lines: 32

In article <1991Mar1.103001.1@dev8h.mdcbbs.com> campbell@dev8h.mdcbbs.com (Tim Campbell) writes:
>
>
>On a VAX, the debugger can run in a graphical or text environment.  Even in
>the text environment, it sets up a 3 or 4 part screen to show code,
>output, commands, etc.
>
>CodeWatch has all the functionality, but it lacks the "window" style 
>environment. - You tell the debugger to list a few lines of code, and after
>a few commands, it's scrolled off the screen and you have to tell it to 
>list more.  DBX has the same problem, but Sun fixed this with the DBXTool to
>provide the graphical/window interface to dbx.  I was really hoping to find
>the same functionality for CodeWatch.

The good news is that a graphical/windowed based interface is now available for
LPI-Codewatch.  X11 and Character-Based versions are available.  

The X11 version uses all the capabilities of the  Motif user interface and X windows.  It provides a source window and a command window.

The character-based interface can run on any ASCII terminal, without a graphical
windowing system.  It provides source, command, and output windows.

For further info,  contact : 
			     Kristen Telford
			     Language Processors, Inc.
			     959 Concord St.
			     Framingham, Ma 01701-4613

			     Telephone: (508) 626-0006
			     Telefax:   (508) 626-2221
			     Telex      951671