This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
dido:public:s_cli:05_contents:01_prt:02_basics:03_paradigim:start [2021/08/13 13:24] murphy |
dido:public:s_cli:05_contents:01_prt:02_basics:03_paradigim:start [2021/10/30 14:51] (current) nick |
||
|---|---|---|---|
| Line 2: | Line 2: | ||
| [[dido:public:s_cli:05_contents:01_prt:02_basics:start| Return to DIDO CLI Background]] | [[dido:public:s_cli:05_contents:01_prt:02_basics:start| Return to DIDO CLI Background]] | ||
| - | Programming paradigms are a way to classify [[dido:public:ra:xapend:xapend.a_glossary:p:programlang|programming languages]] based on their features and characteristics. For example, is the language imperative or declarative in nature. | + | Programming paradigms are a way to classify [[dido:public:ra:xapend:xapend.a_glossary:p:programlang|programming languages]] based on their features and characteristics. For example, is the language [[dido:public:ra:xapend:xapend.a_glossary:i:imperative | Imperative]] or [[dido:public:ra:xapend:xapend.a_glossary:d:declarative | Declarative]] in nature. |
| * //An **Imperative Language** uses a sequence of statements to determine how to reach a certain [[dido:public:ra:xapend:xapend.a_glossary:g:goal|goal]]. These statements are said to change the state of the program as each one is executed in turn. (( | * //An **Imperative Language** uses a sequence of statements to determine how to reach a certain [[dido:public:ra:xapend:xapend.a_glossary:g:goal|goal]]. These statements are said to change the state of the program as each one is executed in turn. (( | ||
| user2102654, | user2102654, | ||
| Line 19: | Line 19: | ||
| An import aspect of any programming language is to determine the programming paradigm(s) features needed to properly and meet the requirements of the language. The DIDO-CLI is no exception. In order to discuss the programming paradigm for DIDO-CLI, a brief overview of the kinds of (i.e., classification) of some of the most common paradigms is presented. | An import aspect of any programming language is to determine the programming paradigm(s) features needed to properly and meet the requirements of the language. The DIDO-CLI is no exception. In order to discuss the programming paradigm for DIDO-CLI, a brief overview of the kinds of (i.e., classification) of some of the most common paradigms is presented. | ||
| - | Some paradigms are place a lot of emphasis on the implications for the execution model of the language, such as allowing side effects, or whether the sequence of operations is defined by the execution model. Other paradigms are concerned mainly with the way that code is organized, such as grouping a code into units along with the state that is modified by the code. Yet others are concerned mainly with the style of syntax and grammar. | + | Some paradigms are place a lot of emphasis on the implications for the execution model of the language, such as allowing side effects, or whether the sequence of operations is defined by the execution model. Other paradigms are concerned mainly with the way that code is organized, such as grouping a code into units along with the state that is modified by the code. Yet others are concerned mainly with the style of [[dido:public:ra:xapend:xapend.a_glossary:s:syntax|syntax]] and grammar. |
| There are many kinds of Programming Paradigms(( | There are many kinds of Programming Paradigms(( | ||