This is sometimes described as "weak typing".

Coercion is usually a symptom of weak typing.

Weak typing allows a value of one type to be treated as another, for example treating a string as a number.

Type systems may be variously static or dynamic, strong or weak typing, and so forth.

The type system of XPath 2.0 is noteworthy for the fact that it mixes strong typing and weak typing within a single language.

He reconfigured his chair for maximum long-term comfort, and placed his beer where he could reach it with his weaker typing hand.

Languages that work like the first three examples have all been called "weak typing" at various times, even though only one of them (the third) represents a safety violation.

Some programmers use the term "weak typing" to refer to languages with type inference, often without realizing that the static type information is present but implicit.

C has a static weak typing type system that shares some similarities with that of other ALGOL descendants such as Pascal.

Consider the process of swapping the values of two variables, x and y. Assuming weak typing and not being concerned about name collision, this is represented by the code:

Untyped atomic values, by contrast, follow a weak typing discipline: they are automatically converted to a type appropriate to the operation where they are used: for example with an arithmetic operation an untyped atomic value is converted to the type .

If an exception is thrown while the data is being processed, for example as described in Strong vs Weak Typing, above, the Dispose method will never be called if the developer writes code explicitly declaring and disposing the DataReader without the use of a try-finally block.