clib2 / Bugs / #50 code relying on char being unsigned

#50 code relying on char being unsigned

Status: closed-fixed

Owner: Olaf Barthel

Labels: None

Priority: 5

Updated: 2010-08-22

Created: 2009-02-13

Creator: Georg Steger

Private: No

The return value of functions like strcmp, memcmp relies on char being unsigned. If char is signed (like with gcc on 68k or x86) return value can be wrong.

(Someone noticed similiar bug in AROS clib and I looked around to see how these functions are done elsewhere)

Discussion

Olaf Barthel - 2010-08-20

assigned_to: nobody --> obarthel
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Olaf Barthel - 2010-08-20

I checked and found that this requirement exists for memcmp(), strcmp() *and* strncmp(), too.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Olaf Barthel - 2010-08-22

status: open --> closed
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Olaf Barthel - 2010-08-22

Fixed in clib2 1.205

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Olaf Barthel - 2010-08-22

status: closed --> closed-fixed
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

code relying on char being unsigned

Group

Searches

Help

#50 code relying on char being unsigned

Discussion