From xemacs-m  Wed Dec 11 14:58:37 1996
Received: from venus.Sun.COM (venus.Sun.COM [192.9.25.5]) by xemacs.cs.uiuc.edu (8.8.3/8.8.3) with SMTP id OAA00795 for <xemacs-beta@xemacs.org>; Wed, 11 Dec 1996 14:58:36 -0600 (CST)
Received: from infodock.com ([206.13.40.192]) by venus.Sun.COM (SMI-8.6/mail.byaddr) with ESMTP id MAA14928; Wed, 11 Dec 1996 12:57:34 -0800
Received: (from weiner@localhost) by infodock.com (8.8.0/8.7.3) id NAA20985; Wed, 11 Dec 1996 13:01:24 -0800
Date: Wed, 11 Dec 1996 13:01:24 -0800
From: Bob Weiner <weiner@infodock.com>
Message-Id: <199612112101.NAA20985@infodock.com>
To: xemacs-beta@xemacs.org
CC: dcw@gcm.com
In-reply-to: <9612102127.AA19038@gsdws133.it.gcm.com> (message from David Worenklein on 10 Dec 1996 16:27:50 -0500)
Subject: Re: Some problems rebuilding lisp files on 19.15-b3


>>>>> "DW" == David Worenklein <dcw@gcm.com> writes:

   DW> During make autoloads
   DW> =====================
   DW> Generating autoloads for /vol/emacs/xemacs-19.15-b3/lisp/modes/eiffel3.el...
   >>> Error processing /vol/emacs/xemacs-19.15-b3/lisp/modes/eiffel3.el: 
   DW> Unbalanced parentheses

This error was fixed in earlier XEmacs distributions.  I believe the problem
was use of a close parentheses character syntax ?) without a backslash to
quote the paren, like so ?\).  (Maybe it was an opening paren.)  The author
then used Emacs auto-paren matching facilities to get the number of close
parens right, but instead added one too few or too many because of the
unescaped syntax character.

Bob

