https://bugzilla.novell.com/show_bug.cgi?id=248719 dcb314@hotmail.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|WONTFIX | ------- Comment #4 from dcb314@hotmail.com 2007-02-28 09:59 MST ------- (In reply to comment #3)
I wonder how it even occured to you to run a build script through valgrind.
I've pretty much done compile time for Suse Linux, so it was time to move onto runtime. I
but without providing an actual bug, it is quite hard to fix it and not break other things.
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. The fix does look difficult, however. I don't understand how providing "an actual bug" is a pre-condition on getting this fixed. You make it sound like code is only broken when it crashes. I'm sure that is not true.
Anyway, as I stated before, this behavior is intended and functional. See this link for thorough discussion of the subject: http://mail.python.org/pipermail/python-dev/2006-November/069892.html
Thanks for the link. I read it - it confirms what I suspected. If I understand correctly, the code is broken, according to the international standards. Is it possible to close this bug report with "fix too hard" ? -- 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.