Return-Path: Delivery-Date: Received: from leopard.cs.byu.edu (no rfc931) by swan.cl.cam.ac.uk with SMTP (PP-6.5) outside ac.uk; Tue, 14 Jun 1994 14:50:28 +0100 Received: by leopard.cs.byu.edu (1.37.109.8/16.2) id AA01339; Tue, 14 Jun 1994 07:50:08 -0600 Sender: hol2000-request@lal.cs.byu.edu Errors-To: hol2000-request@lal.cs.byu.edu Precedence: bulk Received: from crl.dec.com by leopard.cs.byu.edu with SMTP (1.37.109.8/16.2) id AA01335; Tue, 14 Jun 1994 07:50:06 -0600 Received: by crl.dec.com; id AA06174; Tue, 14 Jun 94 09:43:43 -0400 Received: by easynet.crl.dec.com; id AA01592; Tue, 14 Jun 94 09:43:42 -0400 Message-Id: <9406141343.AA01592@easynet.crl.dec.com> Received: from ricks.enet; by crl.enet; Tue, 14 Jun 94 09:43:42 EDT Date: Tue, 14 Jun 94 09:43:42 EDT From: "Tim Leonard, DTN 225-5809, HLO2-3/C11 14-Jun-1994 0940" To: hol2000@leopard.cs.byu.edu Apparently-To: hol2000@leopard.cs.byu.edu Subject: Re: Improved error messages I have to agree with Ralf; error messages should include the operands that caused the error. If printing of huge terms causes a problem, then the term-printing routine should have options for eliding detail. Personally, I'd much rather have the detail and choose to ignore it than to not have the detail. Since I normally see such messages only in an emacs buffer anyway, it's trivial for me to delete anything I don't want to see. Unfortunately, emacs doesn't have a command to add information where it's missing. (I'll have to request that feature.) Tim