Data Types & Type Checking - Ace

More documents

Recommendations

Info

Records vs. Arrays• Arrays mostly used when:– collection of data values is homogenous.– values are process in the same way.– order is important.• Records are used when:– collection of data values is heterogeneous.– values are not precessed in the same way.– unordered.• Access to array elements is much slower than access torecord fields:– array subscripts are dynamic.– record field names are static.Lecture 0634
Unions: Free (Fortran, C/C++)union flex<strong>Type</strong> {int i;double d;bool b;}union flex<strong>Type</strong> ft;ft.i = 27;float x = ft.i; // nonsense, no type checking possible.Lecture 0635
Page 1 and 2: Organization of Programming Languag
Page 3 and 4: Primitive Data Types• Integers -
Page 5 and 6: Scalar Types• Scalar types (also
Page 7 and 8: Array Types• An array is an aggre
Page 9 and 10: Array Categories• Conformant Arra
Page 11 and 12: Implementation of Stack Dynamic Arr
Page 13 and 14: Array Categories• Heap-dynamic: b
Page 15 and 16: Array Initialization• Some langua
Page 17 and 18: Slices• A slice is some substruct
Page 19 and 20: Slices Examples in Fortran 95Lectur
Page 21 and 22: Row vs. Column major orderLecture 0
Page 23 and 24: Contiguous vs. Row Pointer layout i
Page 25 and 26: Access Function for a Multi-Dimensi
Page 27 and 28: Character String Types• Character
Page 29 and 30: Strings in Programming Languages•
Page 31 and 32: Ada Strings• Static Length:X: Str
Page 33: Record Types• C, C++, C#: support
Page 37 and 38: Unions: Discriminated (Algol 68, Ad
Page 39 and 40: Pointer Operations• Two fundament
Page 41 and 42: Problems with Pointers• Dangling
Page 43 and 44: Pointer Arithmetic in C/C++float st
Page 45 and 46: Evaluation of Pointers & References
Page 47 and 48: Type Checking• A type error resul
Page 49 and 50: Strong Typing & Type Coercion• Co

Data Types & Type Checking - Ace

Create successful ePaper yourself

Delete template?

Save as template?