Re: [RFC] Changes to signed char and unsigned char handling

[Nick Roberts <nickrob@snap.net.nz>]

 > >  3.  Treat "char" as a character, but "unsigned char" and "signed char"
 > >  as numbers
 > 
 > Didn't RMS object to this change?

He just said:

  Which GDB behavior is better is a matter of how often each one is
  convenient and how often it causes trouble.  I don't know enough to
  have an opinion about that, but if neither one is clearly better
  overall, it would be best to leave GDB the way it was.

mathieu lacage also said:

  I don't know how useful that is to you but a lot of people (the first
  which comes to my mind is libxml2) decided to use "unsigned char *" to
  identify utf-8 encoded strings in C.

I don't know if this is related to the appearance of xml-builtin.c:

static const char xml_feature_gdb_target_dtd[] = {
  '<', '!', '-', '-', ' ', 'C', 'o', 'p', 'y', 'r', 
   'i', 'g', 'h', 't', ' ', '(', 'C', ')', ' ', '2', 
...

Personally, I'm not worried by this change as my usage has a workaround.

-- 
Nick                                           http://www.inet.net.nz/~nickrob