From xemacs-m  Sun Jun 15 22:39:10 1997
Received: from crystal.WonderWorks.COM (crystal.WonderWorks.com [192.203.206.1])
	by xemacs.org (8.8.5/8.8.5) with ESMTP id WAA04488
	for <xemacs-beta@xemacs.org>; Sun, 15 Jun 1997 22:39:09 -0500 (CDT)
Received: by crystal.WonderWorks.COM 
	id QQcuda02128; Sun, 15 Jun 1997 23:39:10 -0400 (EDT)
Date: Sun, 15 Jun 1997 23:39:10 -0400 (EDT)
Message-Id: <QQcuda02128.199706160339@crystal.WonderWorks.COM>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
From: Kyle Jones <kyle_jones@wonderworks.com>
To: <xemacs-beta@xemacs.org>
Subject: What I learned today.
In-Reply-To: <199706152314.QAA10516@bittersweet.inetarena.com>
References: <199706152314.QAA10516@bittersweet.inetarena.com>
X-Mailer: VM 6.33 under 20.3 "Oslo" XEmacs Lucid (beta7)
X-Face: /cA45WHG7jWq>(O3&Z57Y<"WsX5ddc,4c#w0F*zrV#=M
        0@~@,s;b,aMtR5Sqs"+nU.z^CSFQ9t`z2>W,S,]:[+2^
        Nbf6v4g>!&,7R4Ot4Wg{&tm=WX7P["9%a)_da48-^tGy
        ,qz]Z,Zz\{E.,]'EO+F)@$KtF&V

Karl M. Hegbloom writes:
 >  (preceding-char) and (following-char) return 0 at the boundaries of
 > the buffer, while (char-before 1) and (char-after (point-max)) both
 > return nil.
 > 
 >  It breaks things everywhere, I imagine, and for sure in VM, where the
 > initial assumption is that characters are integers.  (= char ?n) says
 > wrong type argument if char was assigned by (char-after (point-max))
 > and contains nil.

= is different from eq.  Characters are still coerced to integers
in numeric contexts, just as markers are.  (eq ... ...) is not a
numeric context.

