JargonFile/original/html/R/restriction.html
2014-03-27 18:54:56 +00:00

17 lines
2.7 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>restriction</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="../R.html" title="R"/><link rel="previous" href="reply.html" title="reply"/><link rel="next" href="retcon.html" title="retcon"/></head><body><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">restriction</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="reply.html">Prev</a> </td><th width="60%" align="center">R</th><td width="20%" align="right"> <a accesskey="n" href="retcon.html">Next</a></td></tr></table><hr/></div><dt><a id="restriction"/><dt xmlns="" id="restriction"><b>restriction</b>: <span xmlns="http://www.w3.org/1999/xhtml" class="grammar">n.</span></dt></dt><dd><p> A <a href="../B/bug.html"><i class="glossterm">bug</i></a> or design error that limits a program's
capabilities, and which is sufficiently egregious that nobody can quite
work up enough nerve to describe it as a <a href="../F/feature.html"><i class="glossterm">feature</i></a>.
Often used (esp. by <a href="../M/marketroid.html"><i class="glossterm">marketroid</i></a> types) to make it
sound as though some crippling bogosity had been intended by the designers
all along, or was forced upon them by arcane technical constraints of a
nature no mere user could possibly comprehend (these claims are almost
invariably false).</p><p>Old-time hacker Joseph M. Newcomer advises that whenever choosing a
quantifiable but arbitrary restriction, you should make it either a power
of 2 or a power of 2 minus 1. If you impose a limit of 107 items in a
list, everyone will know it is a random number &#8212; on the other hand, a
limit of 15 or 16 suggests some deep reason (involving 0- or 1-based
indexing in binary) and you will get less <a href="../F/flamage.html"><i class="glossterm">flamage</i></a>
for it. Limits which are round numbers in base 10 are always especially
suspect.</p></dd><div class="navfooter"><hr/><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="reply.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="../R.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="retcon.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">reply </td><td width="20%" align="center"><a accesskey="h" href="../index.html">Home</a></td><td width="40%" align="right" valign="top"> retcon</td></tr></table></div></body></html>