> > More specifically, the claim made above: > > > in C I can have a function maximum(int a, int b) that will always > > work. Never blow up, and never give an invalid answer. > > is false. And it is not necessary to invoke the vagaries of run-time > input to demonstrate that it is false. > I don't think you demonstrated it is false. Any values larger than an int get truncated before they ever get to maximum. The problem does not lie with the maximum function. It correctly returns the maximum of whatever two integers it is provided. Calling it with values that are larger than an int, that get converted to an int _before_ maximum is called, is an issue outside of maximum.
-- http://mail.python.org/mailman/listinfo/python-list
