summaryrefslogtreecommitdiff
path: root/ziglings
diff options
context:
space:
mode:
authorDave Gauer <dave@ratfactor.com>2021-02-06 09:29:49 -0500
committerDave Gauer <dave@ratfactor.com>2021-02-06 09:29:49 -0500
commit2cded107cd75a4024d9d0f76055ef48432301fad (patch)
tree3c0b1240e15a60e80d1d3e0d574f06cdfd12b6d6 /ziglings
parent738a9f6cda62f3570e44dc93f8e200afc2cc1b51 (diff)
Add ex 35,36 enums; updated README
I'm changing the order of some more topics. Trying to explain the value of pointers when we're mostly dealing with stack-sized values like integers feels convoluted. So I'm starting with enums (which also has a nice segue from an earlier "switch" exercise). Then structs. Then unions (just in keeping with the order of these items on ziglearn.org) and THEN pointers and multi-pointers and slices.
Diffstat (limited to 'ziglings')
-rwxr-xr-xziglings2
1 files changed, 2 insertions, 0 deletions
diff --git a/ziglings b/ziglings
index be2e829..93b6819 100755
--- a/ziglings
+++ b/ziglings
@@ -102,6 +102,8 @@ check_it 31_switch2.zig "ZIG!"
check_it 32_unreachable.zig "1 2 3 9 8 7"
check_it 33_iferror.zig "2<4. 3<4. 4=4. 5>4. 6>4." "Seriously, what's the deal with fours?"
check_it 34_quiz4.zig "my_num=42" "Can you make this work?"
+check_it 35_enums.zig "1 2 3 9 8 7" "This problem seems familiar..."
+check_it 36_enums2.zig "#0000ff" "I'm feeling blue about this."
echo
echo " __ __ _ "