-
Notifications
You must be signed in to change notification settings - Fork 0
/
imperative.html
103 lines (97 loc) · 5.92 KB
/
imperative.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
<!DOCTYPE html>
<html lang="en" dir="ltr">
<head>
<meta charset="utf-8">
<title>Code Crush for programming paradigms</title>
<link rel="stylesheet" href="style.css">
<script src="https://kit.fontawesome.com/a076d05399.js"></script>
<link rel="apple-touch-icon" sizes="180x180" href="favicon/apple-touch-icon.png">
<link rel="icon" type="image/png" sizes="32x32" href="favicon/favicon-32x32.png">
<link rel="icon" type="image/png" sizes="16x16" href="favicon/favicon-16x16.png">
<link rel="manifest" href="favicon/site.webmanifest">
</head>
<body>
<input type="checkbox" id="check">
<label for="check">
<i class="fas fa-bars" id="btn"></i>
<i class="fas fa-times" id="cancel"></i>
</label>
<div class="sidebar">
<header><i class="fab fa-gratipay"></i>Code Crush</header>
<ul>
<li><a href="index.html"><i class="fas fa-home"></i>Home</a></li>
<li><a href="structural.html"><i class="fas fa-link"></i>Structural</a></li>
<li><a href="procedural.html"><i class="fas fa-stream"></i>Procedural</a></li>
<li><a href="objectoriented.html"><i class="fas fa-angle-double-right"></i>Object Oriented</a></li>
<li><a href="eventdriven.html"><i class="far fa-calendar-check"></i>Event Driven</a></li>
<li><a href="declarative.html"><i class="fas fa-sliders-h"></i>Declarative</a></li>
<li><a href="#"><i class="far fa-envelope"></i>Imperative</a></li>
<li><a href="parallel.html"><i class="fas fa-equals"></i>Parallel</a></li>
<li><a href="concurrent.html"><i class="fas fa-database"></i>Concurrent</a></li>
<li><a href="functional.html"><i class="fas fa-percent"></i>Functional</a></li>
<li><a href="logic.html"><i class="fas fa-sign-in-alt"></i>Logic</a></li>
<li><a href="dependent.html"><i class="fas fa-balance-scale-right"></i>Dependent</a></li>
<li><a href="network.html"><i class="fas fa-wifi"></i>Network</a></li>
<li><a href="symbolic.html"><i class="fas fa-mouse-pointer"></i> Symbolic</a></li>
<li><a href="automata.html"><i class="fas fa-anchor"></i>Automata</a></li>
<li><a href="gui.html"><i class="fas fa-gamepad"></i>GUI</a></li>
</ul>
</div>
<section>
<div class="topnav">
<li><a href="index.html"><i class="fas fa-home"></i> Home</a></li>
<a href="about/index.html"><i class="fas fa-user-circle"></i> About</a>
<a href="https://forms.gle/Dw47JDVJr4tQo7j26"><i class="far fa-bell"></i> Notify</a>
<input type="text" placeholder="Search..">
</div>
<h1>Imperative Programming Paradigms</h1>
<div class="main">
<p>In computer science, imperative programming is a programming paradigm that uses statements that change a program's state. In much the same way that the imperative mood in natural languages expresses commands, an imperative program consists of commands for the computer to perform. Imperative programming focuses on describing how a program operates.</p>
<br>
<p>The term is often used in contrast to declarative programming, which focuses on what the program should accomplish without specifying how the program should achieve the result.</p>
<br>
<p>Imperative programming is a paradigm of computer programming in which the program describes a sequence of steps that change the state of the computer. Unlike declarative programming, which describes "what" a program should accomplish, imperative programming explicitly tells the computer "how" to accomplish it. Programs written this way often compile to binary executables that run more efficiently since all CPU instructions are themselves imperative statements.</p>
</div>
<div class="main2">
<p><span style="color:#52D273;font-weight:bold">MORE ABOUT IMPERATIVE PROGRAMMING</span></p><br>
<p>To make programs simpler for a human to read and write, imperative statements can be grouped into sections known as code blocks. In the 1950s, the idea of grouping a program's code into blocks was first implemented in the ALGOL programming language. They were originally called "compound statements," but today these blocks of code are known as procedures. Once a procedure is defined, it can be used as a single imperative statement, abstracting the control flow of a program and allowing the developer to express programming ideas more naturally. This type of imperative programming is called procedural programming, and it is a step towards higher-level abstractions such as declarative programming.</p>
</div>
<div class="main3">
<p><span style="color:#E95065;font-weight:bold">IMPERATIVE PROGRAMMING LANGUAGES</span></p><br>
<p>Ada<br>
ALGOL<br>
Assembly language<br>
BASIC<br>
Blue<br>
C<br>
C#<br>
C++<br>
D<br>
FORTRAN<br>
Go<br>
Groovy<br>
Java<br>
Julia<br>
Lua<br>
MATLAB<br>
Modula<br>
MUMPS<br>
Nim<br>
Oberon<br>
OCaml<br>
Pascal<br>
Perl<br>
PHP<br>
PROSE<br>
Python<br>
Ruby<br>
Rust</p>
<br>
</div>
<div class="video">
<iframe width="400" height="300" src="https://www.youtube.com/embed/KWD8F2YcYwE" frameborder="0" allow="accelerometer; autoplay; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe>
<img src="images/dvsi.png" alt="paradigm" title="paradigm" width="70%">
</div>
</section>
</body>
</html>