Understanding Data Types and Collections

1. Understanding Data Types and Collections Lesson 2

2. Objective Domain Matrix

3. Data Types in C# • The data type defines the size of memory needed to store the data and the kind of operation that can be performed on the data. • C# is a strongly-typed language. That means the data types for variables, constants , literal values, method return values, and parameters must be known at the compile time.

4. Intrinsic Data Types • Intrinsic data types are the primitive data types for which the support is directly built into the programming language.

5. Values Types and Reference Types • A value type directly stores data within its memory. • Reference types store only a reference to a memory location. The actual data is stored at the memory location being referred to. • When you copy a reference type variable to another variable of the same type, only the references are copied. As a result, after the copy, both variables will point to the same object.

6. Casting • In C#, you can cast an object to any of its base types. • All classes in the .NET Framework inherit either directly or indirectly from the Object class. • Assigning a derived class object to a base class object doesn’t require any special syntax: • Assigning a base class object to a derived class object must be explicitly cast: • At execution time, if the value of o is not compatible with the Rectangle class, the runtime throws a System.InvalidCastException.

7. Boxing and Unboxing • Boxing is the process of converting a value type to the reference type. • Unboxing is the process of converting an object type to a value type. • For unboxing to succeed, you must cast using the same type that was used for boxing. If you use a different data type, you may might get InvalidCastException.

8. Arrays and Collections • The collection data types provide data structures to store and manipulate a collection of items. These collection classes are defined as part of the System.Collections or System.Collections.Generic namespace. • The arrays are special type of collections declared by using a programming language construct. All arrays are internally derived from the System.Array class. • Some common collection data types are arrays, queues, stacks, and linked lists.

9. Demonstration – Cast Object to new type • Cast Employee to Person • Cast Customer to Person • Use the Is keyword to check the type of Person object

10. Arrays • An array is a collection of items of the same type. • The items in an array are stored in contiguous memory locations. • Capacity of an array is predefined and fixed. • Any array item can be directly accessed by using an index. • C# array indexes are zero-based

11. Array - Internal Representation

12. Array – Common Operations • Arrays support the following operations: • Allocation • Access • Thefollowing code assigns a value of 10 to the fourth item of the array, and twice that value is then assigned to the variable calc:

13. Queues • A collection of items in which the first item added to the collection is the first one to be removed. • First In First Out (FIFO) • Queue is a heterogeneous data structure. • Capacity of a queue is the number of items the queue can hold. • As elements are added to the queue, the capacity can be automatically increased.

14. Queues – Internal Representation

15. Queues – Common Operations • Enqueue:Adds an item to the tail end of the queue. • Dequeue:Removes the current element at the head of the queue. • Peek:Access the current item at the head position without actually removing it from the queue. • Contains:Determines whether a particular item exists in the queue.

16. Stacks • A collection of items in which last item added to the collection is the first one to be removed. • Last In First Out (LIFO) • Stack is a heterogeneous data structure. • Capacity of a stack is the number of items the queue can hold. • As elements are added to the stack, the capacity can be automatically increased.

17. Stacks– Internal Representation • A stack can be visualized just like the queue, except that the tail is called the top of the stack and the head is called the bottom of the stack. • New items are always added to the top of a stack; when this happens, the top of the stack starts pointing to the newly added element. • Items are also removed from the top of the stack, and when that happens, the top of the stack is adjusted to point to the next item in the stack.

18. Stack– Common Operations • Push: Adds item to the top of the stack. • Pop: Removes the element at the top of the stack. • Peek:Access the current item at the top of the stack without actually removing it from the stack. • Contains:Determines whether a particular item exists in the stack.

19. Demonstration – Arrays and Collections • Create an Array of Customer Names • Access the Controls Collection of a PlaceHolder control

20. Linked Lists • A linked list is a collection of nodes arranged so that each node contains a link to the next node in the sequence. • Each node in a linked list contains of two pieces of information: • the data corresponding to the node • the link to the next node

21. Linked Lists – Internal Representation • A singly linked list

22. Linked Lists – Internal Representation • A doubly linked list

23. Linked Lists – Common Operations • Add: Adds an item to a linked list. • Remove:Removes a given node from the linked list. • Find:Finds a node with a given value in the linked list.

24. Linked Lists – Visualizing the add operation • Adding an item to a linked list is a matter of changing links.

25. Generics • The Generics feature helps you define classes that can be customized for different data types. • Generics provide many benefits including reusability, type-safety and performance. • The most common use of generics is to create collection classes. 

26. Generics – Definition and Instantiation • The following code illustrates a simple definition of a generic class: • The following code shows how to instantiate a generic class with a concrete type int:

27. Generics – Constraints • Constraints specify restrictions to the kinds of types that client code can use for type arguments when it instantiates your class. • This declaration ensures that when an instance of EmployeeRecord is created, the only valid type arguments are of the type Employee or one of classes derived from the Employee class.

28. Generic Collections • A generic collection is a collection that stores only the items of the same data type. • To ensure type safety, the compiler checks that you can only assign a value of the correct data type from a generic collection. • The generic collection types generally perform better than their non-generic equivalent. With generics there is no need to box and unbox each item.

29. Generic Collections Usage • Generic collections are expressed using a special notation. For example, List<T> is a generic List collection. The T in the notation must be replaced with the data type that you want to store in the collection

30. Common Generic Collections • Some commonly used generic collections:

31. Recap • Data types in the .NET Framework • Intrinsic data types • Value types and reference types • Conversion and casting • Boxing and Unboxing • Arrays and collections • Single dimensional and multi-dimensional arrays • Collection classes • Generics • Generic constraints • Generic Collections

32. Lab – Properties and Methods • Add Property Procedures to classes • Add methods that accept parameters • Add methods that return data