A Brief Description
A Brief Description
A Brief Description
Preface
Computers are some of the most versatile tools that we have available. They are capable of
performing stunning feats of computation, they allow information to be exchanged easily
regardless of their physical location, they simplify many every-day tasks, and they allow us to
automate many processes that would be tedious or boring to perform otherwise. However,
computers are not "intelligent" as we are. They have to be told in no uncertain terms exactly what
they're supposed to do, and their native languages are quite unlike anything we speak. Thus,
there's a formidable language barrier between a person who wishes a computer to do something,
and the computer that typically requires instructions in its native language, machine code, to do
anything. So far, computers cannot figure out what they are supposed to do on their own, and
thus they rely on programs which we create, which are sets of instructions that the computer can
understand and follow.
Depending on the type of project, there are many factors that have to be considered when
choosing a language. Here is a list of some of the more noteworthy ones:
High or Low Level Level, in this case, refers to how much the nature of the language
reflects the underlying system. In other words, a programming language's level refers to
how similar the language is to a computer's native language. The higher the level,
the less similar it is.
A low-level language is generally quite similar to machine code, and thus is more
suitable for programs like device drivers or very high performance programs that really
need access to the hardware. Generally, the term is reserved for machine code itself and
assembly languages, though many languages offer low-level elements. Since a low-level
language is subject to all the nuances of the hardware it's accessing, however, a program
written in a low-level language is generally difficult to port to other platforms. Low level
languages are practically never interpreted, as this generally defeats the purpose.
A high-level language focuses more on concepts that are easy to understand by the
human mind, such as objects or mathematical functions. A high-level language usually is
easier to understand than a low-level language, and it usually takes less time to develop a
program in a high-level language than it does in a low-level language. As a trade-off one
generally needs to sacrifice some degree of control over what the resulting program
actually does. It is not, however, impossible to mix high-level and low-level functionality in
a language.
Type System
A type system refers to the rules that the different types of variables of a language have
to follow. Some languages (including most assembly languages) do not have types and
thus this section does not apply to them. However, as most languages (including C++)
have types, this information is important.
o Type Strength: Strong or Weak
A strong typing system puts restrictions on how different types of variables can be
converted to each other without any converting statements. An ideal strong typing
system would forbid implicit "casts" to types that do not make any sense, such as
an integer to a Fruit object. A weak typing system would try to find some way to
make the cast work.
These typing characteristics are not necessarily mutually exclusive, and some languages
mix them.
Supported paradigms
A programming paradigm is a methodology or way of programming that a programming
language supports. Here is a summary of a few common paradigms:
o Declarative
A declarative language will focus more on specifying what a language is supposed
to accomplish rather than by what means it is supposed to accomplish it. Such a
paradigm might be used to avoid undesired side-effects resulting from having to
write one's own code.
o Functional
Functional programming is a subset of declarative programming that tries to
express problems in terms of mathematical equations and functions. It goes out of
its way to avoid the concepts of states and mutable variables which are common in
imperative languages.
o Generic
Generic programming focuses on writing skeleton algorithms in terms of types that
will be specified when the algorithm is actually used, thus allowing some leniency
to programmers who wish to avoid strict strong typing rules. It can be a very
powerful paradigm if well-implemented.
o Imperative
Imperative languages allow programmers to give the computer ordered lists of
instructions without necessarily having to explicitly state the task. It can be
thought of being the opposite of declarative programming.
o Structured
Structured programming languages aim to provide some form of noteworthy
structure to a language, such as intuitive control over the order in which
statements are executed (if X then do Y otherwise do Z, do X while Y is Z). Such
languages generally deprecate "jumps", such as those provided by the goto
statement in C and C++.
o Procedural
Although it is sometimes used as a synonym for imperative programming, a
procedural programming language can also refer to an imperative structured
programming language which supports the concept of procedures and subroutines
(also known as functions in C or C++).
o Object-Oriented
Object-Oriented programming (sometimes abbreviated to OOP) is a subset of
structured programming which expresses programs in the terms of "objects",
which are meant to model objects in the real world. Such a paradigm allows code
to be reused in remarkable ways and is meant to be easy to understand.
Standardization
Does a language have a formal standard? This can be very important to ensure that
programs written to work with one compiler/interpreter will work with another. Some
languages are standardized by the American National Standards Institute (ANSI), some
are standardized by the International Organization for Standardization (ISO), and some
have an informal but de-facto standard not maintained by any standards organization.