[{Usenet}] 1. To duplicate a portion (or whole) of another's
	message (typically with attribution to the source) in a reply
	or followup, for clarifying the context of one's response.
	See the discussion of inclusion styles under "Hacker Writing
	Style".

	2. [{C}] "#include <disclaimer.h>" has appeared in {sig
	blocks} to refer to a notional "standard {disclaimer} file".

	[{Jargon File}]

<World-Wide Web> A {Java} program which can be distributed as
	an attachment in a {World-Wide Web} document and executed by a
	Java-enabled {web browser} such as Sun's {HotJava},
	{Netscape Navigator} version 2.0, or {Internet Explorer}.

	Navigator severely restricts the applet's file system and
	network access in order to prevent accidental or deliberate
	security violations.  Full Java applications, which run
	outside of the browser, do not have these restrictions.

	Web browsers can also be extended with {plug-ins} though these
	differ from applets in that they usually require manual
	installation and are {platform}-specific.  Various other
	languages can now be embedded within {HTML} documents, the
	most common being {JavaScript}.

	Despite Java's aim to be a "write once, run anywhere"
	language, the difficulty of accomodating the variety of
	browsers in use on the Internet has led many to abandon
	client-side processing in favour of {server}-side Java
	programs for which the term {servlet} was coined.

	Merriam Webster "Collegiate Edition" gives a 1990 definition:
	a short application program especially for performing a simple
	specific task.

	(2002-07-12)

<software> Instructions for a computer in some programming
	language, often {machine language}.  The word "code" is often
	used to distinguish instructions from {data} (e.g. "The code
	is marked 'read-only'") whereas "{software}" is used in
	contrast with "{hardware}" and may consist of more than just
	code.

	(2000-04-08)

<language, architecture> (JVM) A specification for software
	which interprets {Java} programs that have been compiled into
	{byte-codes}, and usually stored in a ".class" file.  The JVM
	{instruction set} is {stack}-oriented, with variable
	instruction length.  Unlike some other instruction sets, the
	JVM's supports {object-oriented} programming directly by
	including instructions for object {method} invocation (similar
	to {subroutine} call in other instruction sets).

	The JVM itself is written in {C} and so can be {ported} to run
	on most {platforms}.  It needs {thread} support and {I/O} (for
	{dynamic class loading}).  The Java byte-code is independent
	of the platform.

	There are also some hardware implementations of the JVM.

	{Specification
	(http://www.javasoft.com/docs/books/vmspec/html/VMSpecTOC.doc.html)}.

	{Sun's Java chip
	(http://news.com/News/Item/0,4,9328,00.html)}.

	[Documentation?  Versions?]

	(2000-01-03)

<testing> The process of exercising a product to identify
	differences between expected and actual behaviour.  Typically
	testing is bottom-up: {unit testing} and {integration testing}
	by developers, {system testing} by testers, and {user
	acceptance testing} by users.

	{Test coverage} attempts to assess how complete a test has
	been.

	2. The second stage in a {generate and test} search
	{algorithm}.

	[{Jargon File}]

	(2003-09-24)

<file system> An element of data storage in a {file system}.

	The history of computing is rich in varied kinds of files and
	{file systems}, whether ornate (e.g., {Macintosh file system}
	for a well-known case) or deficient (e.g., many simple
	pre-1980s file systems don't allow {directories}).

	However, the prototypical file has these characteristics:

	* It is a single sequence of bytes (but consider {Macintosh}
	{resource forks}).

	* It has a finite length, unlike, e.g. a {Unix} {device}.

	* It is stored in a {non-volatile storage} medium (but see
	{ramdrive}).

	* It exists (nominally) in a {directory}.

	* It has a name that it can be referred to by in file
	operations, possibly in combination with its {path}.

	Additionally, a file system may associate other information
	with a file, such as {permission} bits or other {file
	attributes}; timestamps for file creation, last revision, and
	last access; revision numbers (a` la VMS), and other kinds of
	{magic}.

	Compare: {document}.

	(1997-04-08)

<company> The biggest supplier of {operating systems} and
	other software for {IBM PC} compatibles.  Software products
	include {MS-DOS}, {Microsoft Windows}, {Windows NT},
	{Microsoft Access}, {LAN Manager}, {MS Client}, {SQL Server},
	{Open Data Base Connectivity} (ODBC), {MS Mail}, and {SNA
	Server} for Windows NT.

	Microsoft was founded as "Micro-soft" in 1975 by {Bill Gates}
	(now CEO) and his high school pal Paul Allen.  Their first
	product was a version of {BASIC} for the new {Altair} computer
	[which one?].  In 1980, {IBM} chose Microsoft to supply the
	{operating system} for the {IBM PC}.

	On the UK television program "The Net" in May 1994, {Bill
	Gates} said he was betting his company on the {information
	highway}".

	Quarterly sales $1293M, profits $362M (Aug 1994).

	{Home (http://www.microsoft.com/)}.
	{(ftp://ftp.microsoft.com/)}.

	{Interesting Info and Other Microsoft WWW Servers
	(http://www-drg.microsoft.com/devinfo.htm)}.

	{Microsoft Windows Developer Information
	(http://www-drg.microsoft.com/devinfo.htm)}.

	{Microsoft Research Group Information
	(http://www.research.microsoft.com)}.

	{Win_News
	(http://www.microsoft.com/chicago/ms-www/ms-intro.htm)}.
	maintained by the Personal Operating Systems Division to
	distribute information on {Microsoft Windows}, {MS-DOS} and
	{Windows 95}.

	(1998-11-06)

1. <programming> {switch statement}.

	2. <software> {command line option}.

	3. <networking> {packet switch}, {circuit switch}.

	(1999-01-14)

<language, compiler> (JDK) A free {Sun Microsystems} product
	which provides the {environment} required for programming in
	{Java}.  The JDK is available for a variety of {platforms},
	but most notably {Sun Solaris} and {Microsoft Windows}.

	{Home (http://java.sun.com/products/jdk/1.1/index.html)}.

	[Version?]

	(1997-09-04)

<programming> One of a sequence of copies of a program, each
	incorporating new modifications.  Each version is usually
	identified by a number, commonly of the form X.Y where X is
	the major version number and Y is the release number.
	Typically an increment in X (with Y reset to zero) signifies a
	substantial increase in the function of the program or a
	partial or total re-implementation, whereas Y increases each
	time the progam is changed in any way and re-released.

	Version numbers are useful so that the user can know if the
	program has changed ({bugs} have been fixed or new functions
	added) since he obtained his copy and the programmer can tell
	if a bug report relates to the current version.  It is thus
	always important to state the version when reporting bugs.
	Statements about compatibility between different software
	components should always say which versions they apply to.

	See {change management}.

	(1997-12-07)

<language, text> An {SGML}, {HTML}, or {XML} {token}
	representing the beginning (start tag: "<p ...>") or end (end
	tag: "</p>") of an {element}.  In normal SGML {syntax} (and
	always in {XML}), a tag starts with a "<" and ends with an
	">".

	In {HTML} jargon, the term "tag" is often used for an
	"{element}".

	(2001-01-31)

<unit> (b) {binary} digit.

	The unit of information; the amount of information obtained by
	asking a yes-or-no question; a computational quantity that can
	take on one of two values, such as false and true or 0 and 1;
	the smallest unit of storage - sufficient to hold one bit.

	A bit is said to be "set" if its value is true or 1, and
	"reset" or "clear" if its value is false or 0.  One speaks of
	setting and clearing bits.  To {toggle} or "invert" a bit is
	to change it, either from 0 to 1 or from 1 to 0.

	The term "bit" first appeared in print in the computer-science
	sense in 1949, and seems to have been coined by the eminent
	statistician, {John Tukey}.  Tukey records that it evolved
	over a lunch table as a handier alternative to "bigit" or
	"binit".

	See also {flag}, {trit}, {mode bit}, {byte}, {word}.

	[{Jargon File}]

	(2002-01-22)

<jargon> Something (not a person) that loses; a situation in
	which something is losing.  Emphatic forms include "moby
	loss", and "total loss", "complete loss".  Common
	interjections are "What a loss!"  and "What a moby loss!"
	Note that "moby loss" is OK even though **"moby loser" is not
	used; applied to an abstract noun, moby is simply a magnifier,
	whereas when applied to a person it implies substance and has
	positive connotations.

	Compare {lossage}.

	(1995-04-19)

After-sale handholding; something many software vendors
	promise but few deliver.  To hackers, most support people are
	useless - because by the time a hacker calls support he or she
	will usually know the software and the relevant manuals better
	than the support people (sadly, this is *not* a joke or
	exaggeration).  A hacker's idea of "support" is a tte--tte
	or exchange of {electronic mail} with the software's designer.

	[{Jargon File}]

	(1995-02-15)

1. A set of function symbols with {arities}.

	2. <messaging> (Or sig) A few lines of information about the
	sender of an {electronic mail} message or {news} {posting}.
	Most {Unix} mail and news software will {automagically} append
	a signature from a file called .signature in the user's {home
	directory} to outgoing mail and news.

	A signature should give your real name and your {e-mail
	address} since, though these appear in the {headers} of your
	messages, they may be {munged} by intervening software.  It is
	currently (1994) hip to include the {URL} of your {home page}
	on the {World-Wide Web} in your sig.

	The composition of one's sig can be quite an art form,
	including an {ASCII} logo or one's choice of witty sayings
	(see {sig quote}, {fool file}).  However, large sigs are a
	waste of {bandwidth}, and it has been observed that the size
	of one's sig block is usually inversely proportional to one's
	prestige on the net.

	See also {doubled sig}, {sig virus}.

	2. <programming> A concept very similar to {abstract base
	classes} except that they have their own {hierarchy} and can
	be applied to compiled {classes}.  Signatures provide a means
	of separating {subtyping} and {inheritance}.  They are
	implemented in {C++} as patches to {GCC} 2.5.2 by Gerald
	Baumgartner <gb@cs.purdue.edu>.

	{(ftp://ftp.cs.purdue.edu/pub/gb/)}.

	(2001-01-05)

See {tuple}.

1. <file format> A single file containing one or (usually)
	more separate files plus information to allow them to be
	extracted (separated) by a suitable program.

	Archives are usually created for software distribution or
	{backup}.  {tar} is a common format for {Unix} archives, and
	{arc} or {PKZIP} for {MS-DOS} and {Microsoft Windows}.

	2. <operating system> To transfer files to slower, cheaper
	media (usually {magnetic tape}) to free the {hard disk} space
	they occupied.  This is now normally done for long-term
	storage but in the 1960s, when disk was much more expensive,
	files were often shuffled regularly between disk and tape.

	3. <networking> {archive site}.

	(1996-12-08)

<jargon> (spec) A document describing how some system should
	work.

	(2001-02-06)

<job> (Or "computer programmer", "developer") Someone who
	writes or debugs {computer programs}, for a living or for fun.
	"Analyst/developer" is a common equivalent job title, implying
	the added role of {system analysis}.  The term may be
	qualified according to the type of software - "{application}
	programmer", "{system programmer}", etc.

	(2000-01-24)

<programming> (Or "released version", "baseline") A version of
	a piece of software which has been made public (as opposed to
	a version that is in development, or otherwise unreleased).

	A release is either a {major release}, a {revision}, or a
	{bugfix}.

	Pre-release versions may be called {alpha test}, or {beta
	test} versions.

	See {change management}.

	(1996-08-04)

<programming> The first stage of software development which
	defines what the potential users want the system to do.  In
	modern methods these requirements should be testable, and will
	usually be traceable in later development stages.  A common
	feature of nearly all software is that the requirements change
	during its lifetime.

	See {software life-cycle}.

	(1995-11-11)

<hypertext, World-Wide Web, standard> (HTML) A {hypertext}
	document format used on the {World-Wide Web}.  HTML is built
	on top of {SGML}.  "Tags" are embedded in the text.  A tag
	consists of a "<", a "directive" (in lower case), zero or
	more parameters and a ">".  Matched pairs of directives, like
	"<title>" and "</title>" are used to delimit text which is to
	appear in a special place or style.

	Links to other documents are in the form

	 <a href="http://machine.edu/subdir/file.html">foo</a>

	where "<a>" and "</a>" delimit an "anchor", "href" introduces
	a hypertext reference, which is most often a {Uniform Resource
	Locator} (URL) (the string in double quotes in the example
	above).  The link will be represented in the browser by the
	text "foo" (typically shown underlined and in a different
	colour).

	A certain place within an HTML document can be marked with a
	named anchor, e.g.:

	 <a name="baz">

	The "fragment identifier", "baz", can be used in an href by
	appending "#baz" to the document name.

	Other common tags include <p> for a new paragraph, <b>..</b>
	for bold text, <ul> for an unnumbered list, <pre> for
	preformated text, <h1>, <h2> .. <h6> for headings.

	{HTML} supports some standard {SGML} {national characters} and
	other non-{ASCII} characters through special {escape
	sequences}, e.g. "&eacute;" for a lower case 'e' with an acute
	accent.  You can sometimes get away without the terminating
	semicolon but it's bad style.

	Most systems will ignore the case of tags and attributes but
	lower case should be used for compatibility with {XHTML}.

	The {World-Wide Web Consortium} (W3C) is the international
	{standards} body for HTML.

	Latest version: {XHTML} 1.0, as of 2000-09-10.

	{Home (http://www.w3.org/MarkUp/)}.

	{Character escape sequences
	(http://www.w3.org/hypertext/WWW/MarkUp/ISOlat1.html)}.

	See also {weblint}.

	(2006-01-19)

<jargon> To transfer data from one computer to another.
	Downloading usually refers to transfer from a larger "host"
	system (especially a {server} or {mainframe}) to a smaller
	"client" system, especially a {microcomputer} or specialised
	peripheral, and "{upload}" usually means from small to large.

	Others hold that, technically, download means "receive" and
	upload means "send", irrespective of the size of the systems
	involved.

	Note that in communications between ground and space,
	space-to-earth transmission is always "down" and the reverse
	"up", regardless of size.  So far the in-space machines have
	invariably been smaller; thus the upload/download distinction
	has been reversed from its usual sense.

	[{Jargon File}]

	(2003-11-04)