From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mail-relay-2.mv.us.adobe.com ([130.248.1.2]) by hawkwind.utcs.toronto.edu with SMTP id <2740>; Thu, 8 Apr 1993 00:21:27 -0400
Received: by mail-relay-2.mv.us.adobe.com; id AA03489; Wed, 7 Apr 93 21:21:15 -0700
Received: by astro.mv.us.adobe.com; id AA16665; Wed, 7 Apr 93 21:21:54 -0700
Date:	Thu, 8 Apr 1993 00:21:54 -0400
From:	haahr@mv.us.adobe.com (Paul Haahr)
Message-Id: <9304080421.AA16665@astro.mv.us.adobe.com>
To:	john@civil.su.oz.au
Subject: Re:  minor but annoying rc-1.4 bug
Cc:	rc@hawkwind.utcs.toronto.edu

most interpreters suffer from this problem.  that's not saying it's
not a problem, but it's a hard one to fix.  where does the error
for
	fn runtimeerror {
		$1 = fred
	}
	rc -c 'runtimeerror'
get reported.  it really should be tagged to be in at least the
function that caused the problem, as well as the source line that
the was used to create the particular tree node in question.

none of this is impossible, but a solution isn't pretty.  es suffers
from at least as much of the problem, as do other shells in which you
you can write something equivalent.

how would you fix it?  which line would be associated with the error
message?  4, inside the definition of runtimeerror?  9, at the call
to runtimeerror?

paul