Kommandozeilenargumente lesen

A real CLI tool reacts to what the user types after its name. Those words are the command-line arguments, and reading them is step one. 🛠️

Other languages give you a magic argv variable. Zig stays explicit: you ask the std.process namespace for the arguments yourself.

Decoding arguments may allocate memory, so Zig asks you for an allocator up front. No allocation happens behind your back.

Call std.process.argsAlloc with your allocator. It returns a slice of strings, one per argument, that you fully own.

Because you own that slice, you must release it with argsFree. A defer right after the call keeps cleanup automatic.

By convention args[0] is the path to your own program, not user input. The real values you care about start at index 1.

The slice carries its own length, so args.len tells you how many arguments arrived. You check it before reaching for any index.

Iterate the user values by slicing past the program name. A for loop over args[1..] visits each argument in order.

Every argument is a []const u8, a slice of bytes. Comparing or parsing one is just normal Zig string work from here.

Arguments arrive as text. To get a number, parse it with std.fmt.parseInt, which fails clearly if the text is not a valid integer.

Prefer streaming? std.process.argsWithAllocator gives an iterator you advance with next(), handy when you process arguments one at a time.

Think about what sits at the front of the arguments slice.

You read arguments with argsAlloc, freed them with argsFree, skipped args[0], and parsed text into values. Your CLI now hears its user. 🎯