why ¶
Why (and when) would you want to refactor code?
Almost never in practice, because there's usually something more important to do. You only want to refactor a bit of code when that code contains your top priority task or problem, and you can't make progress (that you know will work) or answer a question without refactoring. Some improvements are very hard to assess without comparing alternatives. So sometimes you're best tactic is to try more than one and make an empirical comparison. Refactoring is sometimes the answer when the question was, "Should I change the code from old X to new Y, or to new Z?" and you don't know the answer, but it's important that you end up using the better of the two alternatives Y and Z.
Choose one of these demos for sample code and related docs, developed together to motivate þ C++ code for this purpose.
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
thorn: todo, names, iovec, assert, log, run, hex, crc, buf, in, out, quote, escape, compare, file, deck, cow, arc, blob, tree, slice, rand, time, stat, heap, node, primes, page, book, pile, stack, atomic, lock, mutex, thread, map, meter, list, iter, ctype
The new mu menu links future toy language pages. Many demos are stubs; see todo for a thorn demo guide, or toy for mu updates. Also see names for an overview of naming schemes.
The new mu menu links future toy language pages. Many demos are stubs; see todo for a thorn demo guide, or toy for mu updates. Also see names for an overview of naming schemes.
tech « Þ
