aboutsummaryrefslogtreecommitdiff
path: root/36_enums2.zig
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 /36_enums2.zig
parent738a9f6cda62f3570e44dc93f8e200afc2cc1b51 (diff)
downloadziglings-2cded107cd75a4024d9d0f76055ef48432301fad.tar.gz
ziglings-2cded107cd75a4024d9d0f76055ef48432301fad.tar.bz2
ziglings-2cded107cd75a4024d9d0f76055ef48432301fad.tar.xz
ziglings-2cded107cd75a4024d9d0f76055ef48432301fad.zip
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 '36_enums2.zig')
-rw-r--r--36_enums2.zig61
1 files changed, 61 insertions, 0 deletions
diff --git a/36_enums2.zig b/36_enums2.zig
new file mode 100644
index 0000000..2e04415
--- /dev/null
+++ b/36_enums2.zig
@@ -0,0 +1,61 @@
+//
+// Enums are really just a set of numbers. You can leave the
+// numbering up to the compiler, or you can assign them
+// explicitly. You can even specify the numeric type used.
+//
+// const Stuff = enum(u8){ foo = 16 };
+//
+// You can get the integer out with a built-in function:
+//
+// var my_stuff: u8 = @enumToInt(Stuff.foo);
+//
+// Note how that built-in function starts with "@" just like the
+// @import() function we've been using.
+//
+const std = @import("std");
+
+// Zig lets us write integers in hexadecimal format:
+//
+// 0xf (is the value 15 in hex)
+//
+// Web browsers let us specify colors using a hexadecimal
+// number where each byte represents the brightness of the
+// Red, Green, or Blue component (RGB) where two hex digits
+// are one byte with a value range of 0-255:
+//
+// #RRGGBB
+//
+// Please define and use a pure blue value Color:
+const Color = enum(u32){
+ red = 0xff0000,
+ green = 0x00ff00,
+ blue = ???,
+};
+
+pub fn main() void {
+ // Remeber Zig's multi-line strings? Here they are again.
+ // Also, check out this cool format string:
+ //
+ // {x:0>6}
+ // ^
+ // x type ('x' is lower-case hexadecimal)
+ // : separator (needed for format syntax)
+ // 0 padding character (default is ' ')
+ // > alignment ('>' aligns right)
+ // 6 width (use padding to force width)
+ //
+ // Please add this formatting to the blue value.
+ // (Even better, experiment without it, or try parts of it
+ // to see what prints!)
+ std.debug.print(
+ \\<p>
+ \\ <span style="color: #{x:0>6}">Red</span>
+ \\ <span style="color: #{x:0>6}">Green</span>
+ \\ <span style="color: #{}">Blue</span>
+ \\</p>
+ , .{
+ @enumToInt(Color.red),
+ @enumToInt(Color.green),
+ @enumToInt(???), // Oops! We're missing something!
+ });
+}