Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!ucbvax!CIM-VAX.HONEYWELL.COM!derstad
From: derstad@CIM-VAX.HONEYWELL.COM ("DAVE ERSTAD")
Newsgroups: comp.sys.apollo
Subject: RE: Apollo Pascal
Message-ID: <8905041333.AA03356@umix.cc.umich.edu>
Date: 4 May 89 14:31:00 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 33


I can address some of your questions.  I'm not familar with the ISO
standard for Pascal, so I can't speak to that.

DOMAIN Pascal has no interpreter that I know of.  It does have a powerful
and relatively easy to use debugger (there is an initial learning hump, 
but it's kind of small).  The debugger is DEBUG at SR9.7 (which is good)
or DDE at SR10.X (which from what little use I've made of it is better,
especially for a novice).

There are two profiling type tools.  HPC is bundled and provides a
map of CPU usage within a program.  OK for CPU bound programs.  DPAK
is an extra, but cheap (I think $250 or so?), and is much 
better in two key ways (many smaller ways too).  First, it samples
wait states, so if you have a program which is I/O bound or 
thrashing you can find out where it spending its time.  Second,
you can map both CPU usage and page faults in a "called from"
fashion, rather than for the program as a whole as with HPC.  This
is especially useful when HPC shows that service routine XYZ, called
from 192 separate places in your code, turns out to take all your 
cpu time.  DPAK lets you break down XYZ's time by caller.

Other tools and utilities?  I'm not familar with much pd stuff
for it.  There is a Pascal cross-referencer.  Sometimes useful.

DOMAIN pascal does support separate compilation, but I don't think
it's to any standard, although I could be wrong.

Good Luck!

Dave Erstad
DERSTAD@cim-vax.honeywell.com
Honeywell SSEC