Þ   briarpig  » thorn  » demos  » time


demos are explained here; a menu at top column right indexes actual topic demos. Here we demo time.

problem

     In order to analyze system behavior or to plan resource usage, Wil often needs to measure elapsed time between one place in code and another. This page explains how Wil can cheaply work in units he needs without incurring too much system call overhead.

A submenu for demos appears below, letting you go to the page on a topic written as a demo (as the demos page defines it).

menu

     thorn: todo, names, fd, iovec, assert, log, run, hex, crc, buf, in, out, quote, escape, compare, file, deck, cow, arc, blob, tree, slice, rand, time « Þ, stat, hash, heap, node, primes, page, book, pile, stack, atomic, lock, mutex, thread, map, meter, list, iter, ctype

     (mu: toy, peg, imm, tag, box, symbol, token, number, bigint, class, method, reader, writer, eval, env, vm, gc, world, pcode, compiler, asm, lathe, lisp, smalltalk, design, weight, jar, card, harp, debug, profile)

     Some demos are stubs: todo is a demo guide. See toy for mu updates on language pages; names introduces naming schemes.

stub

     Most of this page is a stub since the page has only been started and not completed. (See todo.)