Projects

pct0 (bonus; due 20190821)

dsi0 (due 20190821)

wcp1 (due 20190821)

pct1 (due 20190828)

wcp2 (due 20190828)

ael0 (due 20190904)

sln0 (due 20190904)

pct2 (due 20190904)

wcp3 (due 20190904)

sln1 (due 20190911)

pct3 (due 20190911)

wcp4 (due 20190911)

sll0 (due 20190918)

pct4 (due 20190918)

wcp5 (due 20190918)

sll1 (due 20190925)

pct5 (due 20190925)

wcp6 (due 20190925)

sll2 (due 20191002)

pct6 (due 20191002)

wcp7 (due 20191002)

sll3 (due 20191009)

sll4 (due 20191009)

pct7 (due 20191009)

wcp8 (due 20191009)

dln0 (due 20191023)

dll0 (due 20191023)

pct8 (bonus; due 20191023)

pct9 (due 20191023)

wcp9 (due 20191023)

dll1 (due 20191030)

pctA (due 20191030)

wcpA (due 20191030)

dll2 (due 20191106)

dls0 (due 20191106)

pctB (due 20191106)

wcpB (due 20191106)

dlq0 (due 20191113)

pctC (due 20191113)

wcpC (due 20191113)

dlt0 (due 20191120)

EoCE (due 20191211)

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.

Table of Contents

Projects

Class Stats

Week 1