Примери за използване на Imperative programming на Английски и техните преводи на Български
{-}
-
Colloquial
-
Official
-
Medicine
-
Ecclesiastic
-
Ecclesiastic
-
Computer
Contrast to imperative programming.
Imperative programming, compared to Declarative programming. .
Comparison to imperative programming.
Imperative programming is the oldest programming paradigm.
Comparison with imperative programming.
In imperative programming, we are giving the program a series of commands to run.
Comparison to imperative programming.
Functional programming is a different basis from imperative programming.
Opposed to the idea of imperative programming is that of declarative programming. .
Higher-order functions are rarely used in older imperative programming.
Imperative programming does have functions, not in the mathematical sense, but in the sense of subroutines.
Comparison with imperative programming.
Functional programming is something complely different from imperative programming.
The opposition to the imperative programming is the case of declarative programming. .
Declarative programming is different from imperative programming.
Imperative programming does have subroutine functions, but these are not functions in the mathematical sense.
This paradigm is called imperative programming.
OOP follows the imperative programming model that relies on a set of primitives that your language provides.
Functional programming is very different from imperative programming.
In contrast, imperative programming changes state with commands in the source code, the simplest example being assignment.
This discussion of the formalization of an algorithm has assumed the premises of imperative programming.
The emphasis on explicit control flow distinguishes an imperative programming language from a declarative programming language.
In contrast, imperative programming changes state with commands in the source language, the most simple example being assignment.
So, while those optimizations are safe in purely functional programming languages,compilers of typical imperative programming usually have to assume the worst.
This is in contrast to Imperative Programming where, in addition to a function's arguments, a global program state can affect a function's resulting value.
A number of concepts and paradigms are specific to functional programming, andgenerally foreign to imperative programming(including object-oriented programming). .
This is the main difference between functional and imperative programming- with imperative the state of the global program can affect the end result of a function.
The most significant differences stem from the fact that functional programming avoids side effects,which are used in imperative programming to implement state and I/O.
When we write a program, we describe step-by-step what the computer must do(at least in imperative programming; in the functional programming things look a bit different) and in most of the cases we rely that the program will execute normally.
In imperative programming languages, the term"conditional statement" is usually used, whereas in functional programming, the terms"conditional expression" or"conditional construct" are preferred, because these terms all have distinct meanings.