example, Unix `make(1)', which returns code 139 for a process
that dies due to {segfault}). 2. A technique that works
acceptably, but which is quite prone to failure if disturbed in the
least. For example, a too-clever programmer might write an
assembler which mapped instruction mnemonics to numeric opcodes
algorithmically, a trick which depends far too intimately on the
particular bit patterns of the opcodes. (For another example of
programming with a dependence on actual opcode values, see {The
Story of Mel, a Real Programmer} in Appendix A.) Many crocks
have a tightly woven, almost completely unmodifiable structure.
See {kluge}, {brittle}. The adjectives `crockish' and
`crocky', and the nouns `crockishness' and `crockitude', are
also used.

:cross-post: [Usenet] /vi./ To post a single article
simultaneously to several newsgroups. Distinguished from posting
the article repeatedly, once to each newsgroup, which causes people
to see it multiple times (which is very bad form). Gratuitous
cross-posting without a Followup-To line directing responses to a
single followup group is frowned upon, as it tends to cause
{followup} articles to go to inappropriate newsgroups when
people respond to only one part of the original posting.

:crudware: /kruhd'weir/ /n./ Pejorative term for the hundreds
of megabytes of low-quality {freeware} circulated by user's
groups and BBS systems in the micro-hobbyist world. "Yet
*another* set of disk catalog utilities for {{MS-DOS}}?
What crudware!"

:cruft: /kruhft/ [back-formation from {crufty}] 1. /n./ An