octave-maintainers
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

8-bit char problem


From: John W. Eaton
Subject: 8-bit char problem
Date: Thu, 10 Oct 2002 16:29:19 -0500

On 10-Oct-2002, Paul Kienzle <address@hidden> wrote:

| Under mingw and cygwin, toascii(setstr(200)) == 72 and
| toascii(setstr(-100)) == 28.  It seems we only have 7-bit 
| characters to work with.

FWIW, this is also what happens on my Debian system:

  bevo:386> octave
  GNU Octave, version 2.1.36 (i386-pc-linux-gnu).
  Copyright (C) 1996, 1997, 1998, 1999, 2000, 2001, 2002 John W. Eaton.
  This is free software; see the source code for copying conditions.
  There is ABSOLUTELY NO WARRANTY; not even for MERCHANTIBILITY or
  FITNESS FOR A PARTICULAR PURPOSE.  For details, type `warranty'.

  Report bugs to <address@hidden>.

  octave:1> toascii(setstr(200)) 
  ans = 72
  octave:2> toascii(setstr(-100)) 
  ans = 28

| I'm recompiling with -funsigned-char to see if I can get
| toascii(setstr(200)) == 200, but the proper solution is 
| to tag all chars with unsigned.

This could be somewhat painful, but I suppose it might be worth doing
it.

jwe



reply via email to

[Prev in Thread] Current Thread [Next in Thread]