GNU bug report logs - #44155
Print integers as characters

Previous Next

Full log

Message #80 received at 44155 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Juri Linkov <juri <at> linkov.net>
Cc: 44155 <at> debbugs.gnu.org, rgm <at> gnu.org, schwab <at> linux-m68k.org
Subject: Re: bug#44155: Print integers as characters
Date: Sun, 01 Nov 2020 21:41:49 +0200

> From: Juri Linkov <juri <at> linkov.net>
> Cc: rgm <at> gnu.org,  44155 <at> debbugs.gnu.org,  schwab <at> linux-m68k.org
> Date: Sun, 01 Nov 2020 21:13:03 +0200
> 
> >> >>  	if (EQ (Vinteger_output_format, Qt) && CHARACTERP (obj)
> >> >> -	    && (c = XFIXNUM (obj)))
> >> >> +	    && (c = XFIXNUM (obj)) && ! CHAR_BYTE8_P (c))
> >> >
> >> > If a test fails, it is better to fix the test and not make the code
> >> > less powerful, don't you agree?
> >> 
> >> This means sweeping the problems under the carpet.
> >
> > Which problem?
> 
> Problem of ambiguous numbers 128 and 4194176 that are both printed as ?\200.

Octal escapes are generally a sign of a raw byte.  This is not
different from buffer display -- how do you know what does ?\200 mean
inside buffer text?

> ?\200 and 128 are two forms of the same character too.

See my question above.  I don't think what you say is true.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.