haas:fall2020:data:projects
This is an old revision of the document!
Table of Contents
Corning Community College
CSCS2320 Data Structures
Assignments, Documents, Information, and Projects
Projects
| ntr0 (bonus; due 20200819) |
| pct1 (bonus; due 20200819) |
| wcp1 (due 20200819) |
| ael0 (due 20200826) |
| pct2 (due 20200826) |
| wcp2 (due 20200826) |
| sln0 (due 20200902) |
| pct3 (due 20200902) |
| wcp3 (due 20200902) |
| sln1 (due 20200909) |
| sll0 (due 20200916) |
| sll1 (due 20200923) |
| sll2 (due 20200930) |
| sll3 (due 20201007) |
| sll4 (due 20201007) |
Class Stats
- status (coming at some point)
Week 1
- Welcome!
- Went over the syllabus, formally introduced ael0 project.
- Started reviewing C by talking about pointers.
- we wrote some sample code
- pointers are a fixed size, regardless of data type
- why? MEMORY ADDRESSING
- on lab46 (running on a 64-bit OS/system), memory addresses are 64-bits (64/8 = 8 bytes)
- so all pointers (whether char, int, float, etc.) will be 8 bytes in size on this system.
- on other systems, notably 16-bit and 32-bit systems (especially late-era hardware that might have incorporated tweaks to support more memory than is typically accessible by the default machine word size), memory address sizes can vary.
- takeaway: for code portability, do not assume 8 byte memory addresses. ALWAYS use sizeof() to maximize portability.
haas/fall2020/data/projects.1597871489.txt.gz · Last modified: 2020/08/19 17:11 by wedge