Files
JargonFile/original/html/C/crock.html
2014-03-27 18:54:56 +00:00

18 lines
3.0 KiB
HTML
Raw Blame History

This file contains invisible Unicode characters
This file contains invisible Unicode characters that are indistinguishable to humans but may be processed differently by a computer. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
<?xml version="1.0" encoding="ISO-8859-1" standalone="no"?>
<html xmlns="http://www.w3.org/1999/xhtml"><head><title>crock</title><link rel="stylesheet" href="../../jargon.css" type="text/css"/><meta name="generator" content="DocBook XSL Stylesheets V1.61.0"/><link rel="home" href="../index.html" title="The Jargon File"/><link rel="up" href="../C.html" title="C"/><link rel="previous" href="crlf.html" title="crlf"/><link rel="next" href="cross-post.html" title="cross-post"/></head><body><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">crock</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="crlf.html">Prev</a> </td><th width="60%" align="center">C</th><td width="20%" align="right"> <a accesskey="n" href="cross-post.html">Next</a></td></tr></table><hr/></div><dt><a id="crock"/><dt xmlns="" id="crock"><b>crock</b>: <span xmlns="http://www.w3.org/1999/xhtml" class="grammar">n.</span></dt></dt><dd><p> [from the American scatologism <span class="firstterm">crock of
shit</span>] </p></dd><dd><p> 1. An awkward feature or programming technique that ought to be made
cleaner. For example, using small integers to represent error codes
without the program interpreting them to the user (as in, for example, Unix
<span class="citerefentry"><span class="refentrytitle">make</span>(1)</span>,
which returns code 139 for a process that dies due to
<a href="../S/segfault.html"><i class="glossterm">segfault</i></a>). </p></dd><dd><p> 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
<a href="../story-of-mel.html" title="The Story of Mel">The Story of Mel'</a> in Appendix A.) Many crocks have a tightly woven,
almost completely unmodifiable structure. See
<a href="../K/kluge.html"><i class="glossterm">kluge</i></a>, <a href="../B/brittle.html"><i class="glossterm">brittle</i></a>. The
adjectives <span class="firstterm">crockish</span> and <span class="firstterm">crocky</span>, and the nouns <span class="firstterm">crockishness</span> and <span class="firstterm">crockitude</span>, are also used.</p></dd><div class="navfooter"><hr/><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="crlf.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="../C.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="cross-post.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">crlf </td><td width="20%" align="center"><a accesskey="h" href="../index.html">Home</a></td><td width="40%" align="right" valign="top"> cross-post</td></tr></table></div></body></html>