https://bugzilla.novell.com/show_bug.cgi?id=248719 ------- Comment #8 from dcb314@hotmail.com 2007-03-01 10:08 MST ------- (In reply to comment #6)
(In reply to comment #4)
I disagree - the code is broken because it fails to conform to ISO C. K&R 2, section 7.8.5 page 167 in my copy.
I'll have to argue with this. K&R is absolutely irrelevant in this case, Python is written in ANSI C, and it's perfectly valid ANSI C.
I agree K&R 1 is irrelevant, that's why I said K&R 2. You can't have it both ways. Either 1. It is valid ISO C 2. It relies on undefined features, and so it isn't ISO C. One or the other, not both. You can't have your cake and eat it.
What you're referring to is the fact that the code relies on "undefined" behavior.
I agree - undefined code doesn't conform to the standards.
* http://mail.python.org/pipermail/python-dev/2006-November/069897.html
I am happy for this bug to be closed as WONTFIX, as long as we both know that there is some undefined code in there which the Python folks won't be fixing anytime soon.
The code is broken when it fails to do what it's supposed to do.
There are lots of other failure modes.
To my best knowledge, there are no standards on what an ANSI C program should do, as long as it's written in proper ANSI C (which it apparently is).
I don't understand this. ISO C defines a standard. Programs written to conform to the standard will behave as the standard specifies. To say that ISO C doesn't define a standard is false. BTW, ANSI C is merely the USA version of the standard. For example, BSI C is the UK version, and DIN C is the German version. I forget the French version. ISO C is the international version. Not all of us live in the USA. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.