missed uninitialised variable warning

[Gabriel Dos Reis]

dewar@gnat.com (Robert Dewar) writes:

| > No.  The reason is that there is no trap representation for unsigned
| > char.   You can safely read an uninitialized unsigned char -- you just
| > get "random"  bit patterns.
| 
| 
| There is absolutely NO justification for this position.

Huh?  Can you provide reference to the protion of the standard that
says otheriwse?

| The formal semantics does not begin to guarantee this behavior.

You're wrong.

| You are just restating the likely  actual behavior of what is
| formally undefined behavior.

No.  That unsigned char don't have trap representation is rule by both
C and C++ standards.

| At least that's my reading of the standard.

Which portion did you read that way?

-- Gaby