| podobné slovo | definícia |
compromise programming
(encz) | compromise programming,kompromisní tvorba programů [eko.] RNDr. Pavel
Piskač |
computer programming
(encz) | computer programming, n: |
linear programming
(encz) | linear programming, n: |
logic programming
(encz) | logic programming, n: |
microprogramming
(encz) | microprogramming,mikroprogramování n: Zdeněk Brož |
monoprogramming
(encz) | monoprogramming,monoprogramování n: Zdeněk Brož |
multiprogramming
(encz) | multiprogramming,multiprogramování n: Zdeněk Brož |
nanoprogramming
(encz) | nanoprogramming,nanoprogramování |
network programming
(encz) | network programming, n: |
object-oriented programming language
(encz) | object-oriented programming language,objektově orientovaný programovací
jazyk n: [it.] Václav Dvořák |
planning-programming-budgeting system
(encz) | planning-programming-budgeting system, |
programming error
(encz) | programming error, n: |
programming language
(encz) | programming language, n: |
reprogramming
(encz) | reprogramming,přeprogramování n: Zdeněk Brož |
small matter of programming
(czen) | Small Matter Of Programming,SMOP[zkr.] |
test instrument planning and programming
(czen) | Test Instrument Planning and Programming,TIPP[zkr.] [voj.] Zdeněk Brož
a automatický překlad |
higher programming language
(gcide) | higher programming language \higher programming language\ n.
(Computers)
A computer programming language with an instruction set
allowing one instruction to code for several assembly
language instructions.
Note: The aggregation of several assembly-language
instructions into one instruction allows much greater
efficiency in writing computer programs. Most programs
are now written in some higher programming language,
such as BASIC, FORTRAN, COBOL, C, C++,
PROLOG, or JAVA.
[PJC] |
programming language
(gcide) | Language \Lan"guage\, n. [OE. langage, F. langage, fr. L. lingua
the tongue, hence speech, language; akin to E. tongue. See
Tongue, cf. Lingual.]
[1913 Webster]
1. Any means of conveying or communicating ideas;
specifically, human speech; the expression of ideas by the
voice; sounds, expressive of thought, articulated by the
organs of the throat and mouth.
[1913 Webster]
Note: Language consists in the oral utterance of sounds which
usage has made the representatives of ideas. When two
or more persons customarily annex the same sounds to
the same ideas, the expression of these sounds by one
person communicates his ideas to another. This is the
primary sense of language, the use of which is to
communicate the thoughts of one person to another
through the organs of hearing. Articulate sounds are
represented to the eye by letters, marks, or
characters, which form words.
[1913 Webster]
2. The expression of ideas by writing, or any other
instrumentality.
[1913 Webster]
3. The forms of speech, or the methods of expressing ideas,
peculiar to a particular nation.
[1913 Webster]
4. The characteristic mode of arranging words, peculiar to an
individual speaker or writer; manner of expression; style.
[1913 Webster]
Others for language all their care express. --Pope.
[1913 Webster]
5. The inarticulate sounds by which animals inferior to man
express their feelings or their wants.
[1913 Webster]
6. The suggestion, by objects, actions, or conditions, of
ideas associated therewith; as, the language of flowers.
[1913 Webster]
There was . . . language in their very gesture.
--Shak.
[1913 Webster]
7. The vocabulary and phraseology belonging to an art or
department of knowledge; as, medical language; the
language of chemistry or theology.
[1913 Webster]
8. A race, as distinguished by its speech. [R.]
[1913 Webster]
All the people, the nations, and the languages, fell
down and worshiped the golden image. --Dan. iii. 7.
[1913 Webster]
9. Any system of symbols created for the purpose of
communicating ideas, emotions, commands, etc., between
sentient agents.
[PJC]
10. Specifically: (computers) Any set of symbols and the
rules for combining them which are used to specify to a
computer the actions that it is to take; also referred to
as a computer lanugage or programming language; as,
JAVA is a new and flexible high-level language which has
achieved popularity very rapidly.
[PJC]
Note: Computer languages are classed a low-level if each
instruction specifies only one operation of the
computer, or high-level if each instruction may specify
a complex combination of operations. Machine language
and assembly language are low-level computer
languages. FORTRAN, COBOL and C are high-level
computer languages. Other computer languages, such as
JAVA, allow even more complex combinations of low-level
operations to be performed with a single command. Many
programs, such as databases, are supplied with special
languages adapted to manipulate the objects of concern
for that specific program. These are also high-level
languages.
[PJC]
Language master, a teacher of languages. [Obs.]
Syn: Speech; tongue; idiom; dialect; phraseology; diction;
discourse; conversation; talk.
Usage: Language, Speech, Tongue, Idiom, Dialect.
Language is generic, denoting, in its most extended
use, any mode of conveying ideas; speech is the
language of articulate sounds; tongue is the
Anglo-Saxon term for language, esp. for spoken
language; as, the English tongue. Idiom denotes the
forms of construction peculiar to a particular
language; dialects are varieties of expression which
spring up in different parts of a country among people
speaking substantially the same language.
[1913 Webster] |
computer programming
(wn) | computer programming
n 1: creating a sequence of instructions to enable the computer
to do something [syn: programming, programing,
computer programming, computer programing] |
linear programming
(wn) | linear programming
n 1: a mathematical technique used in economics; finds the
maximum or minimum of linear functions in many variables
subject to constraints |
logic programming
(wn) | logic programming
n 1: a computer language designed in Europe to support natural
language processing [syn: Prolog, logic programing,
logic programming]
2: creating a program that enables the computer to reason
logically [syn: logic programming, logic programing] |
multiprogramming
(wn) | multiprogramming
n 1: the execution of two or more computer programs by a single
computer [syn: multiprogramming, concurrent execution] |
network programming
(wn) | network programming
n 1: the schedule of programs to be broadcast on a network |
object-oriented programming
(wn) | object-oriented programming
n 1: creating a program that can use and support objects [syn:
object-oriented programming, {object-oriented
programing}] |
object-oriented programming language
(wn) | object-oriented programming language
n 1: (computer science) a programming language that enables the
programmer to associate a set of procedures with each type
of data structure; "C++ is an object-oriented programming
language that is an extension of C" [syn: {object-oriented
programming language}, {object-oriented programing
language}] |
programming error
(wn) | programming error
n 1: error resulting from bad code in some program involved in
producing the erroneous result [syn: software error,
programming error] |
programming language
(wn) | programming language
n 1: (computer science) a language designed for programming
computers [syn: programming language, {programing
language}] |
a hardware programming language
(foldoc) | A Hardware Programming Language
AHPL
(AHPL) A register-level language by Hill and
Peterson, some of whose operators resemble APL.
HPSIM2 is a function-level simulator, available from Engrg
Expt Sta, University of Arizona.
["Digital Systems: Hardware Organization and Design", F. Hill
et al, Wiley 1987].
(1995-01-26)
|
a programming language
(foldoc) | A Programming Language
APL
ISO 8485
(APL) A programming language designed originally by
Ken Iverson at Harvard University in 1957-1960 as a notation
for the concise expression of mathematical algorithms. It
went unnamed (or just called Iverson's Language) and
unimplemented for many years. Finally a subset, APL\360, was
implemented in 1964.
APL is an interactive array-oriented language and programming
environment with many innovative features. It was originally
written using a non-standard character set. It is
dynamically typed with dynamic scope. APL introduced
several functional forms but is not purely functional.
Dyalog APL/W and Visual APL are recognized .NET languages.
Dyalog APL/W, APLX and APL2000 all offer object-oriented
extensions to the language.
ISO 8485 is the 1989 standard defining the language.
Commercial versions: APL SV, VS APL, Sharp APL, Sharp APL/PC,
APL*PLUS, APL*PLUS/PC, APL*PLUS/PC II, MCM APL, Honeyapple,
DEC APL, {APL+Win, APL+Linux, APL+Unix and VisualAPL
(http://www.apl2000.com/)}, {Dyalog APL
(http://www.dyalog.com/)}, {IBM APL2
(http://www-306.ibm.com/software/awdtools/apl/)}, {APLX
(http://www.microapl.co.uk/apl/)}, {Sharp APL
(http://www.soliton.com/services_sharp.html)}
Open source version: NARS2000 (http://www.nars2000.org/).
APL wiki (http://aplwiki.com/).
See also Kamin's interpreters.
APLWEB (http://www.microapl.co.uk/apl/) translates WEB to
APL.
["A Programming Language", Kenneth E. Iverson, Wiley, 1962].
["APL: An Interactive Approach", 1976].
(2009-08-11)
|
ada programming support environment
(foldoc) | Ada Programming Support Environment
APSE
(APSE) A program or set of programs to support
software development in the Ada language.
[Examples?]
(1997-06-30)
|
an evolutionary system for on-line programming
(foldoc) | An Evolutionary System for On-line Programming
AESOP
(AESOP) An early interactive query system on the
IBM 1800 using a light pen.
["AESOP: A Final Report: A Prototype Interactive Information
Control System", J.K. Summers et al, in Information System
Science and Technology, D. Walker ed, 1967].
[Sammet 1969, p. 703].
(1995-04-04)
|
application programming interface
(foldoc) | Application Program Interface
API
Application Programming Interface
Applications Programming Interface
(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)
|
applications programming interface
(foldoc) | Application Program Interface
API
Application Programming Interface
Applications Programming Interface
(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)
|
aspect-oriented programming
(foldoc) | aspect-oriented programming
AOP
(AOP) A style of programming that attempts to
abstract out features common to many parts of the code beyond
simple functional modules and thereby improve the quality of
software.
Mechanisms for defining and composing abstractions are
essential elements of programming languages. The design style
supported by the abstraction mechanisms of most current
languages is one of breaking a system down into parameterised
components that can be called upon to perform a function.
But many systems have properties that don't necessarily align
with the system's functional components, such as failure
handling, persistence, communication, replication,
coordination, memory management, or real-time constraints,
and tend to cut across groups of functional components.
While they can be thought about and analysed relatively
separately from the basic functionality, programming them
using current component-oriented languages tends to result
in these aspects being spread throughout the code. The
source code becomes a tangled mess of instructions for
different purposes.
This "tangling" phenomenon is at the heart of much needless
complexity in existing software systems. A number of
researchers have begun working on approaches to this problem
that allow programmers to express each of a system's aspects
of concern in a separate and natural form, and then
automatically combine those separate descriptions into a final
executable form. These approaches have been called
aspect-oriented programming.
{Xerox AOP homepage
(http://parc.xerox.com/csl/projects/aop/)}.
AspectJ (http://AspectJ.org/).
{ECOOPP'99 AOP workshop
(http://wwwtrese.cs.utwente.nl/aop-ecoop99/)}.
(1999-11-21)
|
basic programming support
(foldoc) | Basic Programming Support
BPS
(BPS, colloquially: Barely
Programming Support) A suite of utility routines from IBM to
perform very simple procedures like formatting a disk or
labelling a tape. BPS was only available on punched cards.
[Dates?]
(1998-07-08)
|
business application programming interface
(foldoc) | Business Application Programming Interface
BAPI
(BAPI) /bap'ee/ A set of
methods provided by an SAP business object.
Release 4.0 of SAP AG's R/3 system supports
object-oriented programming via an interface defined in
terms of objects and methods called BAPIs. For example if
a material object provides a function to check availability,
the corresponding SAP business object type "Material" might
provide a BAPI called "Material.CheckAvailability".
The definitions of SAP business objects and their BAPIs are
kept in an SAP business object repository. SAP provide
classes and libraries to enable a programming team to
build SAP applications that use business objects and BAPIs.
Supported environments include COM and Java.
The {Open BAPI Network
(http://sap.com/solutions/technology/bapis/index.htm)}.
gives background information and lists objects and BAPIs.
(2002-08-30)
|
calendar application programming interface
(foldoc) | Calendar Application Programming Interface
Calendar API
(CAPI, Calendar API) An API for calendar software.
Microsoft has defined a CAPI for their Schedule+
application.
(1995-01-11)
|
cargo cult programming
(foldoc) | cargo cult programming
A style of (incompetent) programming
dominated by ritual inclusion of code or program structures
that serve no real purpose. A cargo cult programmer will
usually explain the extra code as a way of working around some
bug encountered in the past, but usually neither the bug nor
the reason the code apparently avoided the bug was ever fully
understood (compare shotgun debugging, {voodoo
programming}).
The term "cargo cult" is a reference to aboriginal religions
that grew up in the South Pacific after World War II. The
practices of these cults centre on building elaborate mockups
of aeroplanes and military style landing strips in the hope of
bringing the return of the god-like aeroplanes that brought
such marvelous cargo during the war. Hackish usage probably
derives from Richard Feynman's characterisation of certain
practices as "cargo cult science" in his book "Surely You're
Joking, Mr. Feynman" (W. W. Norton & Co, New York 1985, ISBN
0-393-01921-7).
[Jargon File]
(2002-05-28)
|
common isdn application programming interface
(foldoc) | Common ISDN Application Programming Interface
Common-ISDN-API
(CAPI, Common-ISDN-API) A programming interface
standard for an application program to communicate with an
ISDN card.
Work on CAPI began in 1989, focussing on the German ISDN
protocol, and was finished in 1990 by a CAPI working group
consisting of application providers, ISDN equipment
manufacturers, large customers, user groups and DBP Telekom,
resulting in COMMON-ISDN-API Version 1.1. Following
completion of the international protocol specification, almost
every telecommunication provider offers BRI and PRI with
protocols based on Q.931 / ETS 3009 102. Common-ISDN-API
Version 2.0 was developed to support all Q.931 protocols.
(http://capi.org/).
[Why not CIAPI?]
(1998-09-07)
|
computer language for aeronautics and programming
(foldoc) | Computer Language for AeronauticS and Programming
CLASP
(CLASP) A real-time language from NASA, focussing
on fixed-point mathematics. CLASP is a near subset of
SPL, with some ideas from PL/I.
["Flight Computer and Language Processor Study", Raymond
J. Rubey, Management Information Services, Detroit, 1971].
(1994-10-13)
|
computer programming language
(foldoc) | computer programming language
A somewhat redundant term for programming language.
(2014-10-18)
|
concurrent constraint programming
(foldoc) | Concurrent Constraint Programming
(CCP) Not a language, but a general approach.
[Details?]
(2001-11-01)
|
configuration programming
(foldoc) | configuration programming
An approach that advocates the use of a separate
configuration language to specify the coarse-grain structure
of programs. Configuration programming is particularly
attractive for concurrent, parallel and distributed systems
that have inherently complex program structures.
Darwin is an example of a configuration language.
(1995-03-14)
|
constraint functional programming
(foldoc) | constraint functional programming
(CFP) functional programming plus constraints.
(2002-06-08)
|
constraint logic programming
(foldoc) | Constraint Logic Programming
(CLP) A programming framework based (like Prolog)
on LUSH (or SLD) resolution, but in which unification has
been replaced by a constraint solver. A CLP interpreter
contains a Prolog-like inference engine and an {incremental
constraint solver}. The engine sends constraints to the solver
one at a time. If the new constraint is consistent with the
collected constraints it will be added to the set. If it is
inconsistent, it will cause the engine to backtrack.
CLP* is a variant.
["Constraint Logic Programming", J. Jaffar et al, 14th POPL,
ACM 1987].
(1994-11-01)
|
definitional constraint programming
(foldoc) | definitional constraint programming
DCP
(DCP) A declarative, programming paradigm which
integrates concurrent constraint programming, {constraint
logic programming} and functional programming. In this
setting a concurrent constraint language becomes a
coordination system that organises the concurrent interaction
of parallel functional computations. The language is also a
generalisation of parallel functional programming languages,
such as Id, where constraints and constraint abstractions
are reused to define new constraints, as the means of
programming logical variables for parallel coordination.
Goffin is a DCP language.
(1995-03-28)
|
distributed logic programming
(foldoc) | Distributed Logic Programming
(DLP) A logic programming language similar to
Prolog, combined with parallel object orientation similar
to POOL. DLP supports distributed backtracking over the
results of a rendezvous between objects. Multi-threaded
objects have autonomous activity and may simultaneously
evaluate method calls.
["DLP: A Language for Distributed Logic Programming",
A. Eliens, Wiley 1992].
(1996-01-07)
|
eden programming language
(foldoc) | Eden Programming Language
(EPL) A language developed at the {University of
Washington}, based on Concurrent Euclid and used with the
Eden distributed operating system.
EPL influenced Emerald and Distributed Smalltalk.
["EPL Programmer's Guide", A. Black et al, U Washington June
1984].
Eden
|
equational programming language
(foldoc) | Equational Programming Language
(EPL) An equational language for parallel
scientific applications, developed by RPI. Szymanski.
["EPL - Parallel Programming with Recurrent Equations",
B. Szymanski in Parallel Functional Languages and Compilers,
B. Szymanski et al, A-W 1991].
(2010-09-21)
|
esoteric programming language
(foldoc) | esoteric programming language
esolang
(esolang) An intentionally unconventional
computer programming language designed not for practical use
but, rather, to experiment with weird ideas, to be hard to program
in or as a joke.
Brainfuck is one of the best known esolangs.
esolangs.org wiki (http://esolangs.org/).
(2014-10-18)
|
evolutionary programming
(foldoc) | evolutionary programming
(EP) A stochastic optimisation strategy originally conceived
by Lawrence J. Fogel in 1960.
An initially random population of individuals (trial
solutions) is created. Mutations are then applied to each
individual to create new individuals. Mutations vary in the
severity of their effect on the behaviour of the individual.
The new individuals are then compared in a "tournament" to
select which should survive to form the new population.
EP is similar to a genetic algorithm, but models only the
behavioural linkage between parents and their offspring, rather
than seeking to emulate specific genetic operators from nature
such as the encoding of behaviour in a genome and
recombination by genetic crossover.
EP is also similar to an evolution strategy (ES) although
the two approaches developed independently. In EP, selection
is by comparison with a randomly chosen set of other
individuals whereas ES typically uses deterministic
selection in which the worst individuals are purged from the
population.
(1995-02-03)
|
executive systems programming oriented language
(foldoc) | Executive Systems Programming Oriented Language
ESPOL
An ALGOL superset with high level instructions
for low level actions, e.g. interrupting another processor on
a multiprocessor system. Its single pass compiler was very
fast: over 250 lines/s on a 10MHz processor.
ESPOL was used to write the MCP (Master Control Program) on
the Burroughs 6700. It was superseded by NEWP.
["The B6700 ESPOL Reference Manual", Burroughs, 1970].
(2001-06-14)
|
experimental programming language
(foldoc) | Experimental Programming Language
(EPL) A language by David May which influenced
occam.
["EPL: An Experimental Language for Distributed Computing",
D.C. May, in Trends and Applications 1978: Distributed
Processing, NBS, pp.69-71].
(1994-11-18)
|
frobozz magic programming language
(foldoc) | Frobozz Magic Programming Language
FMPL
(FMPL of Accardi). A prototype-based,
object-oriented, event-driven (mainly I/O events) interpreted
language with functional features. Developed at the
Experimental Computing Facility, {University of California,
Berkeley}.
There is an interpreter by Jon Blow
.
(ftp://xcf.berkeley.edu/src/local/fmpl).
Mailing list: .
E-mail: Jack Hsu .
(1992-06-02)
|
functional programming
(foldoc) | functional programming
(FP) A program in a functional language consists
of a set of (possibly recursive) function definitions and
an expression whose value is output as the program's result.
Functional languages are one kind of declarative language.
They are mostly based on the typed lambda-calculus with
constants. There are no side-effects to expression
evaluation so an expression, e.g. a function applied to
certain arguments, will always evaluate to the same value (if
its evaluation terminates). Furthermore, an expression can
always be replaced by its value without changing the overall
result (referential transparency).
The order of evaluation of subexpressions is determined by the
language's evaluation strategy. In a strict
(call-by-value) language this will specify that arguments
are evaluated before applying a function whereas in a
non-strict (call-by-name) language arguments are passed
unevaluated.
Programs written in a functional language are generally
compact and elegant, but have tended, until recently, to run
slowly and require a lot of memory.
Examples of purely functional languages are Clean, FP,
Haskell, Hope, Joy, LML, Miranda, and SML. Many
other languages such as Lisp have a subset which is purely
functional but also contain non-functional constructs.
See also lazy evaluation, reduction.
{Lecture notes
(ftp://ftp.cs.olemiss.edu/pub/tech-reports/umcis-1995-01.ps)}.
or the same {in dvi-format
(ftp://ftp.cs.olemiss.edu/pub/tech-reports/umcis-1995-01.dvi)}.
{FAQ
(http://cs.nott.ac.uk/Department/Staff/gmh/faq.html)}.
{SEL-HPC Article Archive
(http://lpac.ac.uk/SEL-HPC/Articles/)}.
(2003-03-25)
|
functional programming language
(foldoc) | functional programming language
A language that supports and encourages {functional
programming}.
(1995-11-08)
|
generic programming
(foldoc) | generic programming
A programming technique which aims to make
programs more adaptable by making them more general. Generic
programs often embody non-traditional kinds of polymorphism;
ordinary programs are obtained from them by suitably
instantiating their parameters. In contrast with normal
programs, the parameters of a generic programs are often quite
rich in structure. For example they may be other programs,
types or type constructors or even programming
paradigms.
(1997-11-22)
|
generic security service application programming interface
(foldoc) | Generic Security Service Application Programming Interface
GSS-API
(GSS-API) An application level
interface (API) to system security services. It provides a
generic interface to services which may be provided by a
variety of different security mechanisms. Vanilla GSS-API
supports security contexts between two entities (known as
"principals").
GSS-API is a draft internet standard which is being developed
in the Common Authentication Technology Working Group
(cat-wg) of the Internet Engineering Task Force (IETF).
Initial specifications for GSS-API appeared in RFC 1508 and
RFC 1509. Subsequent revisions appeared in several draft
standards documents.
(http://dstc.qut.edu.au/~barton/work/project.html).
(1996-05-19)
|
genetic programming
(foldoc) | genetic programming
(GP) A programming technique which extends the
genetic algorithm to the domain of whole computer programs.
In GP, populations of programs are genetically bred to solve
problems. Genetic programming can solve problems of system
identification, classification, control, robotics,
optimisation, game playing, and pattern recognition.
Starting with a primordial ooze of hundreds or thousands of
randomly created programs composed of functions and terminals
appropriate to the problem, the population is progressively
evolved over a series of generations by applying the
operations of Darwinian fitness proportionate reproduction and
crossover (sexual recombination).
(1995-03-31)
|
genken programming language
(foldoc) | Genken Programming Language
(GPL) A variant of PL360 by K. Asai of the Japan
Atomic Energy Research Institute.
["Experience With GPL", K. Asai, in Machine Oriented Higher
Level Languages, W. van der Poel, N-H 1974, pp. 371-376].
(1995-04-13)
|
illinois functional programming
(foldoc) | Illinois Functional Programming
IFP
(IFP) An interpreter written in portable C by
Arch D. Robison for a variant of Backus's FP with syntax
like ALGOL or Modula-2. IFP Runs under Unix, CTSS
(Cray) and MS-DOS.
Version: 0.5.
(ftp://a.cs.uiuc.edu/pub/ifp). Posted to comp.sources.unix
volume 10.
["The Illinois Functional Programming Interpreter",
A.D. Robison, Proc 1987 SIGPLAN Conf on Interpreters and
Interpretive Techniques (June 1987), pp. 64-73].
["Illinois Functional Programming: A Tutorial", A.D. Robison,
BYTE Feb 1987, pp. 115-125].
(1994-10-24)
|
imperative programming
(foldoc) | imperative language
imperative
imperative programming
Any programming language that specifies explicit
manipulation of the state of the computer system, not to be
confused with a procedural language, which specifies an
explicit sequence of steps to perform.
An example of an imperative (but non-procedural) language is a
data manipulation language for a {relational database
management system}. This specifies changes to the database
but does not necessarily require anyone to specify a sequence
of steps.
Both contrast with declarative languages, which specify
neither explicit state manipulation nor a sequence of steps.
(2007-10-02)
|
industrial programming, inc.
(foldoc) | Industrial Programming, Inc.
The company which developed MTOS.
(http://ipi.com).
E-mail: .
Telephone: +1 (516) 938 6600. Address: 100 Jericho
Quadrangle, Jericho, NY 11753, USA.
(1997-07-23)
|
intermediate programming language
(foldoc) | Intermediate Programming Language
A very early attempt by Arthur W. Burks to express
machine language at a higher level of abstraction. Like
Plankalkul, it used a right-handed style of assignment, in
which the location appears on the right.
(1995-05-09)
|
internet server application programming interface
(foldoc) | Internet Server Application Programming Interface
ISAPI
(ISAPI) Microsoft's programming interface
between applications and their Internet Server. Active
Servers created with ISAPI extensions can be complete
in-process applications themselves, or can "connect" to other
services. ISAPI is used for the same sort of functions as
CGI but uses Microsoft Windows dynamic link libraries
(DLL) for greater efficiency. The server loads the DLL the
first time a request is received and the DLL then stays in
memory, ready to service other requests until the server
decides it is no longer needed. This minimises the overhead
associated with executing such applications many times.
An HTTP server can unload ISAPI application DLLs to free
memory or preload them to speed up the first access.
Applications can also be enhanced by ISAPI filters
(1997-01-06)
|
jam programming language
(foldoc) | JAM Programming Language
(JPL) A string-based imperative language from
JYACC Corporation, part of the JAM tool for developing
screen (non-window) applications.
(2007-10-02)
|
league for programming freedom
(foldoc) | League for Programming Freedom
LPF
(LPF) A grass-roots organisation of professors,
students, businessmen, programmers and users dedicated to
bringing back the freedom to write programs. Once programmers
were allowed to write programs using all the techniques they
knew, and providing whatever features they felt were useful.
Monopolies, software patents and interface copyrights have
taken away freedom of expression and the ability to do a good
job.
"Look and feel" lawsuits attempt to monopolise well-known
command languages; some have succeeded. Copyrights on command
languages enforce gratuitous incompatibility, close
opportunities for competition and stifle incremental
improvements.
Software patents are even more dangerous; they make every
design decision in the development of a program carry a risk
of a lawsuit, with draconian pre-trial seizure. It is
difficult and expensive to find out whether the techniques you
consider using are patented; it is impossible to find out
whether they will be patented in the future.
The League is not opposed to the legal system that Congress
intended -- copyright on individual programs. They aim to
reverse the changes made by judges in response to special
interests, often explicitly rejecting the public interest
principles of the Constitution.
The League works to abolish the monopolies by publishing
articles, talking with public officials, boycotting egregious
offenders and in the future may intervene in court cases. On
1989-05-24, the League picketed Lotus headquarters on
account of their lawsuits, and then again on 1990-08-02.
These marches stimulated widespread media coverage for the
issue.
The League's funds are used for filing briefs; printing
handouts, buttons and signs and whatever will persuade the
courts, the legislators and the people. The League is a
non-profit corporation, but not considered a tax-exempt
charity.
LPF Home (http://progfree.org/).
(2007-02-28)
|
linear programming
(foldoc) | linear programming
A procedure for finding the maximum or minimum
of a linear function where the arguments are subject to
linear constraints. The simplex method is one well known
algorithm.
(1995-04-06)
|
lisp object-oriented programming system
(foldoc) | Lisp Object-Oriented Programming System
(LOOPS) An object-oriented extension of Lisp from the
Intelligent Systems Laboratory at Xerox {Palo Alto
Research Center}. It is used in the development of
knowledge-based systems.
See also CommonLoops.
["The LOOPS Manual", D.G. Bobrow & M. Stefik, Xerox Corp
1983].
|
lisp, objects, and symbolic programming
(foldoc) | LISP, Objects, and Symbolic Programming
A book with compiler included by Robert R. Kessler and Amy
R. Petajan, published by Scott, Foresman and Company,
Glenview, IL, USA. (1988).
|
literate programming
(foldoc) | literate programming
LitProg
Combining the use of a text formatting
language such as TeX and a conventional programming language
so as to maintain documentation and source code together.
Literate programming may use the inverse comment convention.
Perl's literate programming system is called pod.
(2003-09-24)
|
logic programming
(foldoc) | logic programming
A
declarative, relational style of programming based on
first-order logic. The original logic programming language
was Prolog. The concept is based on Horn clauses.
The programmer writes a "database" of "facts", e.g.
wet(water).
("water is wet") and "rules", e.g.
mortal(X) :- human(X).
("X is mortal is implied by X is human"). Facts and rules are
collectively known as "clauses".
The user supplies a "goal" which the system attempts to
prove using "resolution" or "backward chaining". This
involves matching the current goal against each fact or the
left hand side of each rule using "unification". If the
goal matches a fact, the goal succeeds; if it matches a rule
then the process recurses, taking each sub-goal on the right
hand side of the rule as the current goal. If all sub-goals
succeed then the rule succeeds.
Each time a possible clause is chosen, a "choice point" is
created on a stack. If subsequent resolution fails then
control eventually returns to the choice point and subsequent
clauses are tried. This is known as "backtracking".
Clauses may contain logic variables which take on any value
necessary to make the fact or the left hand side of the rule
match a goal. Unification binds these variables to the
corresponding subterms of the goal. Such bindings are
associated with the choice point at which the clause was
chosen and are undone when backtracking reaches that choice
point.
The user is informed of the success or failure of his first
goal and if it succeeds and contains variables he is told what
values of those variables caused it to succeed. He can then
ask for alternative solutions.
(1997-07-14)
|
mail application programming interface
(foldoc) | Messaging Application Programming Interface
Mail Application Programming Interface
MAPI
Messaging Applications Programming Interface
Microsoft Mail Application Program Interface
(MAPI) A messaging architecture and a client
interface component for applications such as {electronic
mail}, scheduling, calendaring and document management. As a
messaging architecture, MAPI provides a consistent interface
for multiple application programs to interact with multiple
messaging systems across a variety of hardware platforms.
MAPI provides better performance and control than {Simple
MAPI}, Common Messaging Calls (CMC) or the {Active Messaging
Library}. It has a comprehensive, open, dual-purpose
interface, integrated with Microsoft Windows. MAPI can be
used by all levels and types of client application and
"service providers" - driver-like components that provide a
MAPI interface to a specific messaging system. For example, a
word processor can send documents and a workgroup
application can share and store different types of data using
MAPI.
MAPI separates the programming interfaces used by the client
applications and the service providers. Every component works
with a common, Microsoft Windows-based user interface. For
example, a single messaging client application can be used to
receive messages from fax, a bulletin board system, a
host-based messaging system and a LAN-based system.
Messages from all of these systems can be delivered to a
single "universal Inbox".
MAPI is aimed at the powerful, new market of workgroup
applications that communicate with such different messaging
systems as fax, DEC All-In-1, voice mail and public
communications services such as AT&T Easylink Services,
CompuServe and MCI MAIL. Because workgroup applications
demand more of their messaging systems, MAPI offers much more
than basic messaging in the programming interface and supports
more than local area network (LAN)-based messaging systems.
Applications can, for example, format text for a single
message with a variety of fonts and present to their users a
customised view of messages that have been filtered, sorted or
preprocessed.
MAPI is built into Windows 95 and Windows NT and can be
used by 16-bit and 32-bit Windows applications. The
programming interface and subsystem contained in the MAPI
DLL provide objects which conform to the {Component Object
Model}. MAPI includes standard messaging client applications
that demonstrate different levels of messaging support.
MAPI provides cross platform support through such industry
standards as SMTP, X.400 and Common Messaging Calls. MAPI
is the messaging component of {Windows Open Services
Architecture} (WOSA).
[Correct expansion? Relatonship with Microsoft?]
(1997-12-03)
|
mathematical analysis without programming
(foldoc) | Mathematical Analysis without Programming
(MAP) An On-line system for mathematics under CTSS.
[Sammet 1969, p. 240].
(1995-02-10)
|
messaging application programming interface
(foldoc) | Messaging Application Programming Interface
Mail Application Programming Interface
MAPI
Messaging Applications Programming Interface
Microsoft Mail Application Program Interface
(MAPI) A messaging architecture and a client
interface component for applications such as {electronic
mail}, scheduling, calendaring and document management. As a
messaging architecture, MAPI provides a consistent interface
for multiple application programs to interact with multiple
messaging systems across a variety of hardware platforms.
MAPI provides better performance and control than {Simple
MAPI}, Common Messaging Calls (CMC) or the {Active Messaging
Library}. It has a comprehensive, open, dual-purpose
interface, integrated with Microsoft Windows. MAPI can be
used by all levels and types of client application and
"service providers" - driver-like components that provide a
MAPI interface to a specific messaging system. For example, a
word processor can send documents and a workgroup
application can share and store different types of data using
MAPI.
MAPI separates the programming interfaces used by the client
applications and the service providers. Every component works
with a common, Microsoft Windows-based user interface. For
example, a single messaging client application can be used to
receive messages from fax, a bulletin board system, a
host-based messaging system and a LAN-based system.
Messages from all of these systems can be delivered to a
single "universal Inbox".
MAPI is aimed at the powerful, new market of workgroup
applications that communicate with such different messaging
systems as fax, DEC All-In-1, voice mail and public
communications services such as AT&T Easylink Services,
CompuServe and MCI MAIL. Because workgroup applications
demand more of their messaging systems, MAPI offers much more
than basic messaging in the programming interface and supports
more than local area network (LAN)-based messaging systems.
Applications can, for example, format text for a single
message with a variety of fonts and present to their users a
customised view of messages that have been filtered, sorted or
preprocessed.
MAPI is built into Windows 95 and Windows NT and can be
used by 16-bit and 32-bit Windows applications. The
programming interface and subsystem contained in the MAPI
DLL provide objects which conform to the {Component Object
Model}. MAPI includes standard messaging client applications
that demonstrate different levels of messaging support.
MAPI provides cross platform support through such industry
standards as SMTP, X.400 and Common Messaging Calls. MAPI
is the messaging component of {Windows Open Services
Architecture} (WOSA).
[Correct expansion? Relatonship with Microsoft?]
(1997-12-03)
|
messaging applications programming interface
(foldoc) | Messaging Application Programming Interface
Mail Application Programming Interface
MAPI
Messaging Applications Programming Interface
Microsoft Mail Application Program Interface
(MAPI) A messaging architecture and a client
interface component for applications such as {electronic
mail}, scheduling, calendaring and document management. As a
messaging architecture, MAPI provides a consistent interface
for multiple application programs to interact with multiple
messaging systems across a variety of hardware platforms.
MAPI provides better performance and control than {Simple
MAPI}, Common Messaging Calls (CMC) or the {Active Messaging
Library}. It has a comprehensive, open, dual-purpose
interface, integrated with Microsoft Windows. MAPI can be
used by all levels and types of client application and
"service providers" - driver-like components that provide a
MAPI interface to a specific messaging system. For example, a
word processor can send documents and a workgroup
application can share and store different types of data using
MAPI.
MAPI separates the programming interfaces used by the client
applications and the service providers. Every component works
with a common, Microsoft Windows-based user interface. For
example, a single messaging client application can be used to
receive messages from fax, a bulletin board system, a
host-based messaging system and a LAN-based system.
Messages from all of these systems can be delivered to a
single "universal Inbox".
MAPI is aimed at the powerful, new market of workgroup
applications that communicate with such different messaging
systems as fax, DEC All-In-1, voice mail and public
communications services such as AT&T Easylink Services,
CompuServe and MCI MAIL. Because workgroup applications
demand more of their messaging systems, MAPI offers much more
than basic messaging in the programming interface and supports
more than local area network (LAN)-based messaging systems.
Applications can, for example, format text for a single
message with a variety of fonts and present to their users a
customised view of messages that have been filtered, sorted or
preprocessed.
MAPI is built into Windows 95 and Windows NT and can be
used by 16-bit and 32-bit Windows applications. The
programming interface and subsystem contained in the MAPI
DLL provide objects which conform to the {Component Object
Model}. MAPI includes standard messaging client applications
that demonstrate different levels of messaging support.
MAPI provides cross platform support through such industry
standards as SMTP, X.400 and Common Messaging Calls. MAPI
is the messaging component of {Windows Open Services
Architecture} (WOSA).
[Correct expansion? Relatonship with Microsoft?]
(1997-12-03)
|
microprogramming
(foldoc) | microcode
microprogramming
A technique for implementing the {instruction
set} of a processor as a sequence of microcode instructions
("microinstructions"), each of which typically consists of a
(large) number of bit fields and the address of the next
microinstruction to execute. Each bit field controls some
specific part of the processor's operation, such as a gate
which allows some functional unit to drive a value onto the
bus or the operation to be performed by the ALU. Several
microinstructions will usually be required to fetch, decode
and execute each machine code instruction
("macroinstruction"). The microcode may also be responsible
for polling for hardware interrupts between each
macroinstruction. Writing microcode is known as
"microprogramming".
Microcode may be classified as "horizontally encoded" or
"vertically encoded". Horizontal microcode is as described
above where there is a fairly direct correspondence between
the bit fields in a microinstruction and the control signals
sent to the various parts of the CPU. Not all combinations of
bits will be valid (e.g. two units driving the bus at once).
Vertical microcode is closer to machine code because a bit
field value may pass through some intermediate combinatory
logic which generates the actual control signals. This allows
a few bits of a microinstruction to determine several control
signals and ensure that only valid combinations of those
signals are generated (e.g. a field may be decoded to determine
which unit drives the bus). The disadvantage with vertical
encoding is that the encoding is usually fixed and takes extra
time compared with horizontal encoding which allows any
combination of signals to be generated and takes no time to
decode.
The alternative to a microcoded processor is a hard-wired
one where the control signals are generated directly from the
bits of the machine code instruction. This is more common
in modern RISC architectures because it is faster.
Microcode is usually stored in ROM chips though some
processors (e.g. the Orion) use fast RAM, making them
dynamically microprogrammable.
(1996-11-26)
|
multiprogramming
(foldoc) | multitasking
concurrency
concurrent processing
multiprogramming
process scheduling
(Or "multi-tasking", "multiprogramming",
"concurrent processing", "concurrency", "process scheduling")
A technique used in an operating system for sharing a single
processor between several independent jobs. The first
multitasking operating systems were designed in the early
1960s.
Under "cooperative multitasking" the running task decides
when to give up the CPU and under "pre-emptive multitasking"
(probably more common) a system process called the
"scheduler" suspends the currently running task after it has
run for a fixed period known as a "time-slice". In both
cases the scheduler is responsible for selecting the next task
to run and (re)starting it.
The running task may relinquish control voluntarily even in a
pre-emptive system if it is waiting for some external event.
In either system a task may be suspended prematurely if a
hardware interrupt occurs, especially if a higher priority
task was waiting for this event and has therefore become
runnable.
The scheduling algorithm used by the scheduler determines
which task will run next. Some common examples are
round-robin scheduling, priority scheduling, {shortest job
first} and guaranteed scheduling.
Multitasking introduces overheads because the processor
spends some time in choosing the next job to run and in saving
and restoring tasks' state, but it reduces the worst-case time
from job submission to completion compared with a simple
batch system where each job must finish before the next one
starts. Multitasking also means that while one task is
waiting for some external event, the CPU to do useful work
on other tasks.
A multitasking operating system should provide some degree of
protection of one task from another to prevent tasks from
interacting in unexpected ways such as accidentally modifying
the contents of each other's memory areas.
The jobs in a multitasking system may belong to one or many
users. This is distinct from parallel processing where one
user runs several tasks on several processors. Time-sharing
is almost synonymous but implies that there is more than one
user.
Multithreading is a kind of multitasking with low
overheads and no protection of tasks from each other, all
threads share the same memory.
(1998-04-24)
|
new programming language
(foldoc) | NEW Programming language
NEWP
(NEWP) A language which replaced ESPOL on the
Burroughs Large System.
(1994-12-13)
|
object-oriented programming
(foldoc) | object-oriented programming
object-oriented language
object-oriented programming language
OOP
OOPL
(OOP) The use of a class of programming
languages and techniques based on the concept of an "object"
which is a data structure (abstract data type) encapsulated
with a set of routines, called "methods", which operate on
the data. Operations on the data can __only__ be performed via
these methods, which are common to all objects that are
instances of a particular "class". Thus the interface to
objects is well defined, and allows the code implementing the
methods to be changed so long as the interface remains the
same.
Each class is a separate module and has a position in a
"class hierarchy". Methods or code in one class can be
passed down the hierarchy to a subclass or inherited from a
superclass. This is called "inheritance".
A procedure call is described as invoking a method on an
object (which effectively becomes the procedure's first
argument), and may optionally include other arguments. The
method name is looked up in the object's class to find out how
to perform that operation on the given object. If the method
is not defined for the object's class, it is looked for in its
superclass and so on up the class hierarchy until it is found
or there is no higher superclass.
OOP started with SIMULA-67 around 1970 and became
all-pervasive with the advent of C++, and later Java.
Another popular object-oriented programming language (OOPL) is
Smalltalk, a seminal example from Xerox's {Palo Alto
Research Center} (PARC). Others include Ada, {Object
Pascal}, Objective C, DRAGOON, BETA, Emerald, POOL,
Eiffel, Self, Oblog, ESP, LOOPS, POLKA, and
Python. Other languages, such as Perl and VB, permit,
but do not enforce OOP.
FAQ (http://iamwww.unibe.ch/~scg/OOinfo/FAQ/).
(http://zgdv.igd.fhg.de/papers/se/oop/).
(http://cuiwww.unige.ch/Chloe/OOinfo).
Usenet newsgroup: news:comp.object.
(2001-10-11)
|
object-oriented programming language
(foldoc) | object-oriented programming
object-oriented language
object-oriented programming language
OOP
OOPL
(OOP) The use of a class of programming
languages and techniques based on the concept of an "object"
which is a data structure (abstract data type) encapsulated
with a set of routines, called "methods", which operate on
the data. Operations on the data can __only__ be performed via
these methods, which are common to all objects that are
instances of a particular "class". Thus the interface to
objects is well defined, and allows the code implementing the
methods to be changed so long as the interface remains the
same.
Each class is a separate module and has a position in a
"class hierarchy". Methods or code in one class can be
passed down the hierarchy to a subclass or inherited from a
superclass. This is called "inheritance".
A procedure call is described as invoking a method on an
object (which effectively becomes the procedure's first
argument), and may optionally include other arguments. The
method name is looked up in the object's class to find out how
to perform that operation on the given object. If the method
is not defined for the object's class, it is looked for in its
superclass and so on up the class hierarchy until it is found
or there is no higher superclass.
OOP started with SIMULA-67 around 1970 and became
all-pervasive with the advent of C++, and later Java.
Another popular object-oriented programming language (OOPL) is
Smalltalk, a seminal example from Xerox's {Palo Alto
Research Center} (PARC). Others include Ada, {Object
Pascal}, Objective C, DRAGOON, BETA, Emerald, POOL,
Eiffel, Self, Oblog, ESP, LOOPS, POLKA, and
Python. Other languages, such as Perl and VB, permit,
but do not enforce OOP.
FAQ (http://iamwww.unibe.ch/~scg/OOinfo/FAQ/).
(http://zgdv.igd.fhg.de/papers/se/oop/).
(http://cuiwww.unige.ch/Chloe/OOinfo).
Usenet newsgroup: news:comp.object.
(2001-10-11)
|