By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
435,247 Members | 1,057 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 435,247 IT Pros & Developers. It's quick & easy.

unsigned char and -1

P: n/a
I came across the following piece of code:

#define ERROR -1
#define STATUS0 0
#define STATUS1 1
#define STATUS2 2

unsigned char foo()
{
if (/* condition-A */) return ERROR; /* is that safe? */
if (/* condition-B */) return STATUS0;
if (/* condition-C */) return STATUS1;
return STATUS2;
}

Is '-1 returned as unsigned char' safe in the given context?
Alex Vinokur
email: alex DOT vinokur AT gmail DOT com
http://mathforum.org/library/view/10978.html
http://sourceforge.net/users/alexvn

Oct 25 '05 #1
Share this Question
Share on Google+
7 Replies


P: n/a
Alex Vinokur wrote:
I came across the following piece of code:

#define ERROR -1
#define STATUS0 0
#define STATUS1 1
#define STATUS2 2

unsigned char foo()
{
if (/* condition-A */) return ERROR; /* is that safe? */
if (/* condition-B */) return STATUS0;
if (/* condition-C */) return STATUS1;
return STATUS2;
}

Is '-1 returned as unsigned char' safe in the given context?


In the given (restricted) context, yes, it returns UCHAR_MAX.
[Any value not in the range of an unsigned type is converted
modulo 1+UTYPE_MAX.]

However, in broader contexts, it's not so safe, e.g. ...

if (foo() == ERROR)

This condition will likely fail even though foo returns ERROR.
This is because the UCHAR_MAX will likely be promoted to a
int, and -1 is not UCHAR_MAX.

--
Peter

Oct 25 '05 #2

P: n/a

"Peter Nilsson" <ai***@acay.com.au> wrote in message news:11**********************@o13g2000cwo.googlegr oups.com...
Alex Vinokur wrote:
I came across the following piece of code:

#define ERROR -1
#define STATUS0 0
#define STATUS1 1
#define STATUS2 2

unsigned char foo()
{
if (/* condition-A */) return ERROR; /* is that safe? */
if (/* condition-B */) return STATUS0;
if (/* condition-C */) return STATUS1;
return STATUS2;
}

Is '-1 returned as unsigned char' safe in the given context?
In the given (restricted) context, yes, it returns UCHAR_MAX.
[Any value not in the range of an unsigned type is converted
modulo 1+UTYPE_MAX.]

However, in broader contexts, it's not so safe, e.g. ...

if (foo() == ERROR)


And in this context?

unsigned char ch1, ch2;
ch1 = foo();
/* Stuff-1 */
if (ch1 == ch2)
{
/* Stuff-2 */
}

This condition will likely fail even though foo returns ERROR.
This is because the UCHAR_MAX will likely be promoted to a
int, and -1 is not UCHAR_MAX.

[snip]
--
Alex Vinokur
email: alex DOT vinokur AT gmail DOT com
http://mathforum.org/library/view/10978.html
http://sourceforge.net/users/alexvn


Oct 25 '05 #3

P: n/a

Alex Vinokur wrote:
And in this context?

unsigned char ch1, ch2;
ch1 = foo();
/* Stuff-1 */
if (ch1 == ch2)
{
/* Stuff-2 */
}


and in this context ch2 is undefined :-p

Oct 25 '05 #4

P: n/a

<ma************@gmail.com> wrote in message news:11*********************@g47g2000cwa.googlegro ups.com...

Alex Vinokur wrote:
And in this context?

unsigned char ch1, ch2;
ch1 = foo();
/* Stuff-1 */
if (ch1 == ch2)
{
/* Stuff-2 */
}


and in this context ch2 is undefined :-p


Stuff-1 can change ch2.
--
Alex Vinokur
email: alex DOT vinokur AT gmail DOT com
http://mathforum.org/library/view/10978.html
http://sourceforge.net/users/alexvn

Oct 25 '05 #5

P: n/a
Alex Vinokur wrote:
I came across the following piece of code:

#define ERROR -1
#define STATUS0 0
#define STATUS1 1
#define STATUS2 2

unsigned char foo()
{
if (/* condition-A */) return ERROR; /* is that safe? */ [...] Is '-1 returned as unsigned char' safe in the given context?


[comp.lang.c answer]
Yes, it is safe in the sense that UCHAR_MAX will be returned.
No, it is not safe, because 'ERROR' invades the namespace reserved to
the implementation.

As a general rule, crossposting to comp.lang.c and comp.lang.c++ is a
poor idea. Not only are these different languages, but when the syntax
is the same in each language, the semantics may differ, and when the
syntax and semantics agree, the accepted best practice may differ.
Oct 25 '05 #6

P: n/a

Alex Vinokur wrote:
unsigned char ch1, ch2;
ch1 = foo();
/* Stuff-1 */
if (ch1 == ch2)
{
/* Stuff-2 */
}


and in this context ch2 is undefined :-p


Stuff-1 can change ch2.


A comment can change variable? Now that's something new :-p''

Oct 25 '05 #7

P: n/a
Martin Ambuhl wrote:
Alex Vinokur wrote:
I came across the following piece of code:

#define ERROR -1
#define STATUS0 0
#define STATUS1 1
#define STATUS2 2

unsigned char foo()
{
if (/* condition-A */) return ERROR; /* is that safe? */

[...]
Is '-1 returned as unsigned char' safe in the given context?


[comp.lang.c answer]
Yes, it is safe in the sense that UCHAR_MAX will be returned.
No, it is not safe, because 'ERROR' invades the namespace reserved
to the implementation.


True, although EXXXX identifiers are only reserved if the code
includes <errno.h>. That said, it is best to avoid defining such
identifiers at all, in case the code ever gets included by other
code that might use <errno.h>.

--
Peter

Oct 26 '05 #8

This discussion thread is closed

Replies have been disabled for this discussion.