|
Stand-alone is a confusing and misleading term, used to refer to various categories of computer programs, but rarely in a consistent fashion. The term usually tries to draw some distinction between programs that are run directly by the user by giving some kind of command to the operating system and those programs that are invoked by other programs.
But this distinction does not stand up to scrutiny, since the computer has to be running some kind of program that receives the user command to begin with, thus all programs are launched by other programs (with the sole exception of the bootstrap loader), and there is really no such thing as code that "stands alone".
Another distinction might be drawn between those programs that run as operating system processes and those that are loaded as an add-on to the context of an existing process, such as a plugin. This distinction may make sense, except that here the term "stand-alone" has been used inconsistently: for instance, on the Macintosh platform, it was often the plugin code that was referred to as "stand-alone".
A less ambiguous terminology would refer to "application" and "non-application" code, since "application" seems to be a commonly-accepted cross-platform term for a program that runs as a separate process, invoked as a direct result of some user action. The "non-application" code then has to be loaded and run as part of the process context of the "application" code, and there is no ambiguity about which is which.
In computer games, a "stand-alone" game is one that can be played without another game to provide most of its operating code (as opposed to an expansion pack, which is explicitly an add-on to a previous game).
| 
