"Strong typing vs. strong testing"

TheFlyingDutchman zzbbaadd at aol.com
Fri Oct 1 08:28:42 CEST 2010

> >         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. If someone
> >         tries to call it incorrectly it is a compile error.
> I would agree that the third sentence is arguably wrong, simply
> because there's no such thing (outside #error) of a mandate to stop
> compiling.  However, my understanding was that the dispute was over
> the second sentence, and that's certainly correct.
Why do you consider the term "compile error" a "mandate to stop
compiling"? What do you say to refer to the situation when you have a
statement in your program that the compiler finds is an error? And is
it really material whether the compiler flagged an error and stopped,
or flagged an error and looked for additional errors???

More information about the Python-list mailing list