Toolkit

Hey guys, I'm putting together a toolkit of commonly used things that I can plug into programs rather than writing them from scratch every time and I want to know what I should put in it.

So far I've got a stack, doubly-linked list, double-ended queue, and binary search/sort algorithms.

What else does /prog/ think I should put in there?

>>7
Along this line of thought x86 Assembler is the best teaching language, but just maybe I'd start with a scripting language or basic. BTW, you can't write an OS-kernel in C alone, both NT and Linux kernels are optimized in assembler or straight-forward machine code(you can't write firmware even on assembler).

OP: you include things in your libraries as they become relevant that way they don't have a lot of cool sounding functions, which will you never need.