"Strong typing vs. strong testing"

[Keith Thompson]

Seebs <usenet-nospam at seebs.net> writes:
> On 2010-10-01, TheFlyingDutchman <zzbbaadd at aol.com> wrote:
>>> > ? ? ? ? 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"?
>
> Because that's what people normally mean -- compilation failed.

At least for C, I'd say it refers to a syntax error or constraint
violation, i.e., something that requires a diagnostic.

[...]

-- 
Keith Thompson (The_Other_Keith) kst-u at mib.org  <http://www.ghoti.net/~kst>
Nokia
"We must do something.  This is something.  Therefore, we must do this."
    -- Antony Jay and Jonathan Lynn, "Yes Minister"