From xemacs-m  Fri Mar 21 00:25:10 1997
Received: from altair.xemacs.org (steve@xemacs.miranova.com [206.190.83.19])
	by xemacs.org (8.8.5/8.8.5) with ESMTP id AAA00110
	for <xemacs-beta@xemacs.org>; Fri, 21 Mar 1997 00:25:04 -0600 (CST)
Received: (from steve@localhost)
	by altair.xemacs.org (8.8.5/8.8.5) id WAA08354;
	Thu, 20 Mar 1997 22:36:32 -0800
Mail-Copies-To: never
To: xemacs-beta@xemacs.org
Subject: Re: XEmacs 19.15-b102 is released
References: <m2rah93l2z.fsf@altair.xemacs.org> <kig913hsroc.fsf@jagor.srce.hr>
X-Url: http://www.miranova.com/%7Esteve/
X-Face: #!T9!#9s-3o8)*uHlX{Ug[xW7E7Wr!*L46-OxqMu\xz23v|R9q}lH?cRS{rCNe^'[`^sr5"
 f8*@r4ipO6Jl!:Ccq<xoV[Qz2u8<8-+Vwf2gzJ44lf_/y9OaQ`@#Q65{U4/TC)i2`~/M&QI$X>p:9I
 OSS'2{-)-4wBnVeg0S\O4Al@)uC[pD|+
X-Attribution: sb
From: Steven L Baur <steve@miranova.com>
In-Reply-To: Hrvoje Niksic's message of 21 Mar 1997 07:08:35 +0100
Mime-Version: 1.0 (generated by tm-edit 7.105)
Content-Type: text/plain; charset=US-ASCII
Date: 20 Mar 1997 22:36:30 -0800
Message-ID: <m22099n441.fsf@altair.xemacs.org>
Lines: 56
X-Mailer: Gnus v5.4.33/XEmacs 20.1(beta9)

Hrvoje Niksic writes:

> Steven L Baur <steve@miranova.com> writes:
>> * Richard Mlynarik suggested the broken functions preceding-char and
>> following-char be made obsolete.
> [...]
>> -- preceding-char, following-char are obsolete and broken, do not
>> use them

> Please, when you do this, make sure that there is at least a mention
> of what should be used instead.  E.g.:

That happens by default, by the way.

What they say now:
C-h f preceding-char
preceding-char: (&optional BUFFER)
  -- a built-in function.
Obsolete; use `char-after' instead.

Return the character preceding point.
At the beginning of the buffer or accessible region, return 0.
If BUFFER is nil, the current buffer is assumed.

C-h f following-char
following-char: (&optional BUFFER)
  -- a built-in function.
Obsolete; use `char-after' instead.

Return the character following point.
At the end of the buffer or accessible region, return 0.
If BUFFER is nil, the current buffer is assumed.

> `following-char' is obsolete blah blah(...); use `(char-after (point))'
> instead.

> BTW, what should be used for `preceding-char'?  `(char-after (1- (point)))'
> doesn't look satisfactory, somehow.

Something on the order of:
(defsubst char-before (pos)
  "Return character in BUFFER at position POS.
POS is an integer or a buffer pointer.
If POS is out of range, the value is nil."
  (char-after (1- pos)))

perhaps?

> P.S.
> In what way are they ({preceding,followin}-char) broken, other than
> the infamous 0 lossage?

Isn't that enough?
-- 
steve@miranova.com baur
Unsolicited commercial e-mail will be billed at $250/message.

