4 ms·
> and is basically the entire reason for choosing strongly typed language like Java in the first place. Technical nitpicking: It's best to avoid using the term
by Tade0 9y ago
> and is basically the entire reason for choosing strongly typed language like Java in the first place.
Technical nitpicking: It's best to avoid using the terms "strong" and "weak" when referring to type systems, since they don't have clear, agreed upon definitions.
Some would say that Java is not a strongly typed language since its type system isn't sound.
- ben-schaaf 9y agoJust to add to this, the better terms to use are "static" and "dynamic". Going with the example of a sound type system, a language could have a sound type system that does the actual checking at runtime.
- dozzie 9y agoNo, not really. Even though there's no good definition what "strong" and "weak" means, it was always meant as a totally different axis than static/dynamic typing. C is weakly typed, OCaml is strongly typed. Both are typed statically.
- catnaroek 9y agoA type soundness theorem is always of the form “a well-typed program never does such and such”. It relates the static semantics (type checking) to the dynamic semantics (operational semantics) of a programming language. It doesn't make any sense to talk about soundness for dynamic languages, because there's no static semantics to relate to the dynamic semantics.