signed is undefined and has been since 1992 (in GCC)

[Gabriel Dos Reis]

Robert Dewar <dewar@adacore.com> writes:

[...]

| > The issue is whether they need to become expect in red herring or just
| > know how to write good and correct programs.  Interestingly, backis
| > the old days K&R put emphasis on how to write good and useful programs
| > rather than academic exercise in "undefined behaviour".
| 
| Actually K&R, which of course is definitely NOT a standard, and did indeed
| leave a lot of things undefined, not deliberately, but just by imprecision
| or omission, is, nevertheless, more precise than people think, and did
| introduce the notion of undefined constructs.

Notice that it is one thing to know about undefined construct, and
another to know how to write correct codes.  And that in trun is
different from being imprecise.  That was the point. 

| I find it surprising that you would disagree with the propoosition that
| more C programmers should be familiar with the C standard.
| 
| And I must say, that if you think the worry about undefined behavior is
| academic, I have to strongly disagree. You may be able to take this

What is surprising to me is how you reach such conclusions.

-- Gaby