Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!ucsd!dog.ee.lbl.gov!pasteur!eden.Berkeley.EDU!mao
From: mao@eden.Berkeley.EDU (Mike Olson)
Newsgroups: comp.unix.ultrix
Subject: Re: ds5000/200 Ultrix4 dbx problems
Message-ID: <28939@pasteur.Berkeley.EDU>
Date: 19 Oct 90 00:51:18 GMT
References: <26832@cs.yale.edu>
Sender: news@pasteur.Berkeley.EDU
Reply-To: mao@postgres.Berkeley.EDU.UUCP (Mike Olson)
Organization: University of California, Berkeley
Lines: 19

In <26832@cs.yale.edu>, weier@twolf4.CE.YALE.EDU (Richard Weier) writes

> It appears that dbx for the DS5000 provides no way of calling a function.
> Why has the extremely handy "call" command been removed?  This drastically
> cuts into our development efficiency!

as TFM explains, "call" is "func" using dec's dbx.  apparently compatibility
wasn't the first thing on their minds.  there are other minor annoyances;
having the last action repeated when you hit carriage return really sucks
when you have a bouncy keyboard, and making ^D behave non-deterministically
was a bad idea.  the list goes on...

curse me for a heathen, but i *really* wish there were an adb for the
pmax chip, and we could stop compiling such obese programs.  still, even
dec's dbx beats printf()'s.
					mike olson
					postgres research group
					uc berkeley
					mao@postgres.berkeley.edu