24 ;;Quote: computer memory is fundamentally typeless. Any word can hold any value
|
24+;;Quote: the meaning of a value in computer memory is determined by use; it may have multiple meanings
|
25 ;;Quote: scripting languages are usually typeless; makes it easy to reuse and connect components
|
25+;;Quote: scripting languages are often string-oriented; provides a uniform representation for many different things
|
25+;;Quote: unlike object-oriented systems, scripting languages have generated significant software reuse
|
25 ;;Quote: strong typing discourages reuse through incompatible interfaces; it does not raise the level of programming
|
25+;;Quote: raising the level of programming should be the single most important goal of a language. It has a large effect on productivity
|
25 ;;Quote: Tcl can define a button with a single line. The same button takes 7 lines of code in Java and 25 lines in C++/MFC
|
25+;;Quote: strong typing in C++ leads to extra code; e.g., SetFont requires an initialized CFont object
|
26 ;;Quote: the primitive operations of scripting languages are more powerful than those of system programming languages; e.g., regular expression substitution and variable traces for updating the display
|
27 ;;Quote: scripting languages can develop gluing applications 5 to 10 times faster than a system programming language
|
27+;;Quote: a system programming language can often run 10 to 20 times faster than a scripting language
|
29 ;;Quote: the strong typing of most object-oriented languages encourages narrowly defined packages that are hard to reuse
|
29+;;Quote: object-oriented programming leads to a modest increase in productivity
|
29 ;;Quote: implementation inheritance is a bad idea that binds implementations together so that all classes must be understood together; like 'goto' statements
|
29 ;;Quote: encapsulation and interface inheritance are useful features of object-oriented programming
|