New subject: Char-related crashes (hopefully) fixed

Monday, 15 November 1999

        Note: it should really be int-char and char-int, not int-to-char and
char-to-int.

Yoshiki Hayashi <t90553(a)m.ecc.u-tokyo.ac.jp&gt; writes:

...
 > This is exactly the kind of code that we should disallow.  What
 > does each of those 558 characters mean when inserted in the
 > buffer?  Surely most of them are not characters in any known
 > character set.  Should they be inserted?  Ignored?  Do you tell
 > the user what you've done?  In which functions do you want to put
 > the checking code?  What are you supposed to do with the integers
 > that are not characters: signal an error, display a warning, set a
 > flag for user code to check?

 Signal an error. 
I hope you don't propose that int-char signals an error.  It would be
a serious breach of compatibility.  What should happen is that it
returns nil, just as before.  (insert nil) will, of course, signal an
error.

...
 Desired code is like this

 (let ((i 32))
   (while (< i 128)
     (insert (make-char 'latin-iso8859-9 i))
     (setq i (1+ i)))) 
Yup.  That's where we all agree.

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

1999

1998

Re: Char-related crashes (hopefully) fixed