JargonFile/original/html/U/unixism.html
2014-03-27 18:54:56 +00:00

20 lines
2.8 KiB
HTML
Raw Permalink 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>unixism</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="../U.html" title="U"/><link rel="previous" href="Unix-weenie.html" title="Unix weenie"/><link rel="next" href="unswizzle.html" title="unswizzle"/></head><body><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">unixism</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="Unix-weenie.html">Prev</a> </td><th width="60%" align="center">U</th><td width="20%" align="right"> <a accesskey="n" href="unswizzle.html">Next</a></td></tr></table><hr/></div><dt><a id="unixism"/><dt xmlns="" id="unixism"><b>unixism</b>: <span xmlns="http://www.w3.org/1999/xhtml" class="grammar">n.</span></dt></dt><dd><p> A piece of code or a coding technique that depends on the protected
multi-tasking environment with relatively low process-spawn overhead that
exists on virtual-memory Unix systems. Common
<a href="unixism.html"><i class="glossterm">unixism</i></a>s include: gratuitous use of
<span class="citerefentry"><span class="refentrytitle">fork</span>(2)</span>;
the assumption that certain undocumented but well-known features of Unix
libraries such as
<span class="citerefentry"><span class="refentrytitle">stdio</span>(3)</span>
are supported elsewhere; reliance on <a href="../O/obscure.html"><i class="glossterm">obscure</i></a>
side-effects of system calls (use of
<span class="citerefentry"><span class="refentrytitle">sleep</span>(2)</span>
with a 0 argument to clue the scheduler that you're willing to give up your
time-slice, for example); the assumption that freshly allocated memory is
zeroed; and the assumption that fragmentation problems won't arise from
never
<span class="citerefentry"><span class="refentrytitle">free</span>()</span>ing
memory. Compare <a href="../V/vaxocentrism.html"><i class="glossterm">vaxocentrism</i></a>; see also
<a href="../N/New-Jersey.html"><i class="glossterm">New Jersey</i></a>.</p></dd><div class="navfooter"><hr/><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="Unix-weenie.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="../U.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="unswizzle.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Unix weenie </td><td width="20%" align="center"><a accesskey="h" href="../index.html">Home</a></td><td width="40%" align="right" valign="top"> unswizzle</td></tr></table></div></body></html>