<operating system> See {Microsoft Windows}, {Windows NT}.

	(1997-11-23)

<programming> (API, or "application programming interface")
	The interface (calling conventions) by which an {application
	program} accesses {operating system} and other services.  An
	API is defined at {source code} level and provides a level of
	{abstraction} between the application and the {kernel} (or
	other privileged utilities) to ensure the {portability} of the
	code.

	An API can also provide an interface between a {high level
	language} and lower level utilities and services which were
	written without consideration for the {calling conventions}
	supported by compiled languages.  In this case, the API's main
	task may be the translation of parameter lists from one format
	to another and the interpretation of {call-by-value} and
	{call-by-reference} arguments in one or both directions.

	(1995-02-15)

1. The art of debugging a blank sheet of paper (or, in these
	days of on-line editing, the art of debugging an empty file).

	2. A pastime similar to banging one's head against a wall, but
	with fewer opportunities for reward.

	3. The most fun you can have with your clothes on (although
	clothes are not mandatory).

	[{Jargon File}]

	(2003-02-12)

1. <storage> {Main memory} or {RAM}.  This term dates from the
	days of {ferrite core memory}; now archaic most places outside
	{IBM}, but also still used in the {Unix} community and by
	old-time {hackers} or those who would sound like them.

	Some derived idioms are quite current; "in core", for example,
	means "in memory" ({paged in}, as opposed to "on disk", {paged
	out}), and both {core dump} and the "core image" or "core
	file" produced by one are terms in favour.  Some varieties of
	Commonwealth hackish prefer {store}.

	[{Jargon File}]

	(1995-03-03)

	2. <processor> An {integrated circuit} design, usually for a
	{microprocessor}, which includes only the {CPU} and which is
	intended to form part of a complete circuit design which
	incorporates other circuits on the same chip such as {cache},
	{memory management unit}, I/O ports and timers.

	The {ARM6}, {ARM7} and {ARM8} are examples.

	3. <language> A varient on {kernel} as used to describe
	features built into a language as opposed to those provided by
	{libraries}.

	(1995-03-03)

<messaging> 1. {electronic mail}.

	2. The {Berkeley Unix} program for composing and reading
	{electronic mail}.  It normally uses {sendmail} to handle
	delivery.

	{Unix manual page}: mail(1)

	(1997-12-03)

<security> (By analogy with biological viruses, via SF) A
	program or piece of code written by a {cracker} that "infects"
	one or more other programs by embedding a copy of itself in
	them, so that they become {Trojan horses}.  When these
	programs are executed, the embedded virus is executed too,
	thus propagating the "infection".  This normally happens
	invisibly to the user.

	A virus has an "engine" - code that enables it to propagate
	and optionally a "payload" - what it does apart from
	propagating.  It needs a "host" - the particular hardware and
	software environment on which it can run and a "trigger" - the
	event that starts it running.

	Unlike a {worm}, a virus cannot infect other computers without
	assistance.  It is propagated by vectors such as humans
	trading programs with their friends (see {SEX}).  The virus
	may do nothing but propagate itself and then allow the program
	to run normally.  Usually, however, after propagating silently
	for a while, it starts doing things like writing "cute"
	messages on the terminal or playing strange tricks with the
	display (some viruses include {display hacks}).  Viruses
	written by particularly antisocial {crackers} may do
	irreversible damage, like deleting files.

	By the 1990s, viruses had become a serious problem, especially
	among {IBM PC} and {Macintosh} users (the lack of security on
	these machines enables viruses to spread easily, even
	infecting the operating system).  The production of special
	{antivirus software} has become an industry, and a number of
	exaggerated media reports have caused outbreaks of near
	hysteria among users.  Many {lusers} tend to blame
	*everything* that doesn't work as they had expected on virus
	attacks.  Accordingly, this sense of "virus" has passed into
	popular usage where it is often incorrectly used for a {worm}
	or {Trojan horse}.

	See {boot virus}, {phage}.  Compare {back door}.  See also
	{Unix conspiracy}.

	[{Jargon File}]

	(2003-06-20)

1. The {supervisor} program or {operating system} on a
	computer.

	2. The entire computer system, including input/output devices,
	the {supervisor} program or {operating system} and possibly
	other {software}.

	3. Any large program.

	4. Any method or {algorithm}.

	[{Jargon File}]

Specific computer hardware, as in the phrase
	"platform-independent".  It may also refer to a specific
	combination of hardware and {operating system} and/or
	{compiler}, as in "this program has been ported to several
	platforms".  It is also used to refer to support software for
	a particular activity, as in "This program provides a platform
	for research into routing protocols".

	(1994-12-07)