| slovo | definícia |
implementation
(mass) | implementation
- implementácia |
implementation
(encz) | implementation,implementace n: |
implementation
(encz) | implementation,provedení n: Zdeněk Brož |
implementation
(encz) | implementation,realizace n: Zdeněk Brož |
implementation
(encz) | implementation,realizační n: Zdeněk Brož |
implementation
(encz) | implementation,uskutečnění n: Zdeněk Brož |
implementation
(encz) | implementation,zavedení n: Zdeněk Brož |
implementation
(wn) | implementation
n 1: the act of accomplishing some aim or executing some order;
"the agency was created for the implementation of the
policy" [syn: execution, implementation, {carrying
out}]
2: the act of implementing (providing a practical means for
accomplishing something); carrying into effect [syn:
implementation, effectuation] |
| | podobné slovo | definícia |
implementation lag
(encz) | implementation lag,implementační zpoždění [eko.] RNDr. Pavel Piskač |
implementations
(encz) | implementations,implementace n: Zdeněk Brož |
joint implementation
(encz) | joint implementation,společná implementace [eko.] RNDr. Pavel Piskač |
reimplementation
(encz) | reimplementation,reimplementace n: Zdeněk Brož |
report on implementation of standards and codes
(encz) | Report on Implementation of Standards and Codes, |
asdo implementation language
(foldoc) | ASDO IMPlementation Language
ASDIMPL
(ASDIMPL) A C-like language, run on Burroughs'
mainframes in the early 1980s, and cross-compiled to
x86-based embedded processors.
(1996-02-06)
|
basic language for implementation of system software
(foldoc) | Basic Language for Implementation of System Software
BLISS
(BLISS, or allegedly, "System Software
Implementation Language, Backwards") A language designed by
W.A. Wulf at CMU around 1969.
BLISS is an expression language. It is block-structured,
and typeless, with exception handling facilities,
coroutines, a macro system, and a highly {optimising
compiler}. It was one of the first non-assembly languages
for operating system implementation. It gained fame for its
lack of a goto and also lacks implicit dereferencing: all
symbols stand for addresses, not values.
Another characteristic (and possible explanation for the
backward acronym) was that BLISS fairly uniformly used
backward keywords for closing blocks, a famous example being
ELUDOM to close a MODULE. An exception was BEGIN...END though
you could use (...) instead.
DEC introduced the NOVALUE keyword in their dialects to allow
statements to not return a value.
Versions: CMU BLISS-10 for the PDP-10; CMU BLISS-11,
BLISS-16, DEC BLISS-16C, DEC BLISS-32, BLISS-36 for
VAX/VMS, BLISS-36C.
["BLISS: A Language for Systems Programming", CACM
14(12):780-790, Dec 1971].
[Did the B stand for "Better"?]
(1997-03-01)
|
bottom-up implementation
(foldoc) | bottom-up implementation
The opposite of top-down design. It is now
received wisdom in most programming cultures that it is best
to design from higher levels of abstraction down to lower,
specifying sequences of action in increasing detail until you
get to actual code. Hackers often find (especially in
exploratory designs that cannot be closely specified in
advance) that it works best to *build* things in the opposite
order, by writing and testing a clean set of primitive
operations and then knitting them together.
[Jargon File]
(1996-05-10)
|
implementation language
(foldoc) | IMPlementation language
(IMP) An extension of B with floating-point
operations, developed by W. Davidsen at General Electric in
1970 for the GE 600. It was also cross-compiled to VAX
and Intel 8080.
(1996-04-07)
|
bottom-up implementation
(jargon) | bottom-up implementation
n.
Hackish opposite of the techspeak term top-down design. It has been
received wisdom in most programming cultures that it is best to design from
higher levels of abstraction down to lower, specifying sequences of action
in increasing detail until you get to actual code. Hackers often find
(especially in exploratory designs that cannot be closely specified in
advance) that it works best to build things in the opposite order, by
writing and testing a clean set of primitive operations and then knitting
them together. Naively applied, this leads to hacked-together bottom-up
implementations; a more sophisticated response is middle-out implementation
, in which scratch code within primitives at the mid-level of the system is
gradually replaced with a more polished version of the lowest level at the
same time the structure above the midlevel is being built.
|
middle-out implementation
(jargon) | middle-out implementation
See bottom-up implementation.
|
|