Now that you've taken the midterm, you probably have different ideas about how this section should be run. Please visit the following URL:
http://depts.washington.edu/ctlt/catalyst/umail/mail.cgi?user=keunwoo&form=1
Answer the following 3 questions:
- Which of the following do you think we should spend more time on? Which less?
- review of lecture material
- lecture on novel material beyond regular lecture
- in-class exercises
- Name one way you think section could be improved.
- Name one thing I should not change about section, if anything.
- stack
- Area of memory in which local/automatic storage is allocated. Memory in the stack is freed whenever the procedure for the corresponding activation record returns.
- heap/free store
- Area of memory in which dynamic memory is allocated using new. Memory allocated in the heap must be explicitly deallocated using delete or delete [].
- memory leak
- Failure to release dynamic memory before the last pointer to it has been lost.
- dangling pointer
- Pointer that refers to memory that has been deallocated or is otherwise invalid.
- garbage collection
- Automatic memory management provided by the runtime system, which guarantees that neither memory leaks nor dangling pointers are possible. Not available in most C++ implementations.
- null pointer
- Pointer whose value is NULL or 0 (they are equivalent), and therefore invalid. Note that on most machine architectures, memory cannot be stored at location 0.