Quote: the difference between dynamic and static type checking is the difference between "x must be a car" and "x is a car" [»stroB_1991]

Quote: static type-checking may not catch type errors due to subclassing a function argument [»alexRT1_2000]

Quote: with static typing can detect procedure-call errors early but lose generic procedures and requires type declarations [»teslL8_1981]

Quote: check routines for class invariants are an invaluable help during debugging and class definition [»stroB_1991]

Quote: production code should include some of the check routines for class invariants

Quote: type consistency should be checked as soon as sufficient information is available; unifies static and dynamic typing [»heerJ4_1985]

Quote: in an improperly functioning system, procedures can get unexpected data [»robsD8_1981]

Quote: with a weakly-typed language, inconsistencies are not caught until run-time

Quote: while some operators apply to many types, others apply to restricted types, e.g., division [»hehnEC7_1975]

Quote: some values of composite types are invalid; need run-time checks, e.g., array bounds [»kiebRB9_1973, OK]

Quote: use TYPECASE to test the referent type of any traced object [»cardL_1991]

Quote: fast dynamic casting using 64-bit type ID and a prime number for each class; requires whole program analysis, e.g., embedded system [»gibbM2_2006]

Quote: use display mechanism for run-time access to extended type descriptors; construct at compile time [»coheNH10_1991]

Quote: C++ run-time type mechanism: 'dynamic_cast' from a base class, an explicit 'typeid', and implementation 'type_info' [»stroB_1994]

Quote: PL.8 not standardized despite being a fully-checked language; enforcement of language rules cost less than 10% [»auslM6_1982]

Quote: PL.8 guarantees that all array and offset references are within bounds; optimizes run-time checks; checking costs 5-10% [»auslM6_1982]

Quote: Cyclone is a safe dialect of C; avoids buffer overflows, format string attacks, and memory management errors; static analysis plus run-time checks and annotations [»jimT6_2002]

Quote: Cyclone has growable memory region, tagged union, polymorphism, and exceptions

Quote: a system should be intelligent, i.e., help the user and reduce workload; e.g., check all inputs for validity [»potaWA_1979]

Quote: a function interface should lead to correct code; avoid multiple returns, error values, and multipurpose functions; allow strong argument validation [»maguS_1993]

Quote: a validated element must match its type, since validation yields sensible values; consequence of pure named typing [»simeJ1_2003]

Quote: validation methods are primarily used as bug-finders; formal methods are useful because they find different bugs than traditional methods; a more realistic goal than guaranteeing correctness [»dillDL4_1996]

Quote: enforce type system with run-time validation checks on each argument; e.g., all file names belong to the /tmp directory

Quote: typetest operators to test literals; e.g., 'isn x' is true if x is a number [»wirtN1_1966]

Quote: Cyclone has never-NULL pointers (@...) and fat pointers (?...) with run-time checking (e.g., varargs) [»jimT6_2002]

Quote: check all pointer and array accesses with an extended safe pointer representation; 2-6x time cost, less than 2x space cost [»austTM6_1994]

Quote: safe pointer representation with base address, size, storage class, and liveness property; check all accesses with unnecessary checks avoided via runtime tests [»austTM6_1994]

Quote: SafeTSA includes safe-ref that cannot be null, and safe-index-arr that cannot be out of range; via runtime checks [»ammeW6_2001]

Quote: an application can test the validity of a link and correct the link if necessary [»ashmH9_2000]

Quote: use the page fault handler to implement quick page accessibility tests; a page fault only occurs on a negative answer [»liedJ1_1994]

Quote: subtype testing via PQ-trees; small footprint, constant time; originally used in constraint ordering [»zibiY10_2001]

Quote: object-oriented database can check method arguments at invocation instead of at transaction commit [»smitKE10_1987]

Quote: since variables do not have a static type; the Smalltalk compiler can not detect message errors at compilation [»teslL8_1981]

Quote: inheritance allows for polymorphic variables to become attached at run-time [»meyeB9_1990]

Quote: an entity is declared with a static type and associated with a dynamic type at runtime; all dynamic types must be descendants

Quote: Smalltalk is safe since type mismatches ('message not understood') are reported with a notify window [»teslL8_1981]

Quote: most common Smalltalk error is 'message not understood' [»teslL8_1981]

Quote: a flavor is a property of an object that changes during program execution; e.g., 'total' may be initialized, partial sum, total sum [»howdWE1_1990]

Quote: SafeTSA is compact, type-safe mobile code based on static single assignment; safe by construction with referential integrity, type separation, and type check elimination [»ammeW6_2001]

Quote: use typeflow analysis to detect errors and reduce dynamic type testing of Oberon-style types [»cornD3_1994]

Quote: runtime overhead of PQL ranges from 9% to 125%; static analysis helps a lot; max is 19x slowdown [»martM10_2005]

Quote: dynamic type checking underspecifies an interface; it makes an assumption that is checked at runtime

Quote: dynamic type checking can make a program run 3 to 10 times slower than the same program with static type checking [»stroB_1991]