User Tools

Site Tools


Sidebar

Welcome to DIDO WIKI

dido:public:ra:1.2_views:3_taxonomic:4_data_tax:08_objects:07_opers:start

This is an old revision of the document!


2.3.4.8.4 Operation Data

Overview

Return to Top

Any particular operation within an Object is generally Imperative in nature. This means that the Operations are composed of a set of statements. As the program steps through the Operation and executes each statement (i.e., instruction) the state of the Object is changed. Some statements change the values of the Field Data while others change the flow of execution through Control Flow operations (i.e., IF / ELSE IF / ELSE / ENDIF, or FOR LOOPS | WHILE LOOPS /, etc.). As the statements are executed, the Program Counter for the Operation is also modified. Note: Rarely all the statements contained within a single operation, but relies on calling and executing other Operations. Therefore, most Operations are also considered a Procedural Language. Figure 1 provides a graphic of the difference between Imperative and Procedural Programs.

Figure 1: The difference between Imperative and Procedural Programming.

To confuse the situation even more, there is a differentiation between the Imperative or Procedural: function, procedure, and method.

function a named set of instructions that perform a task and return a single value to the caller of the function. Generally, all the parameters passed to the function are considered IN (i.e., Read-Only).
procedure
  • Dividing an integer by zero.
  • Accessing an element that is out of range of the array
  • Trying to store a value into an array that is not compatible type
  • Passing an argument that is not in a valid range or valid value for a method
  • Striving to use a negative size for an array
  • Attempting to convert an invalid string into a number

DIDO Specifics

Return to Top

An interesting phenomenon about many of the DIDO Platforms, is the way they treat Operation Data. Many of the Platforms not only distribute Field Data using Distributed Ledger or Journal, they also distribute the Operation Data in the same way (in essence, treating the software just as any other data). When changes are made to the Operation Data, a Transaction is created to be pushed to the Node Network.

General Methods

Return to Top

[char]New Section -- review

dido/public/ra/1.2_views/3_taxonomic/4_data_tax/08_objects/07_opers/start.1636233598.txt.gz · Last modified: 2021/11/06 17:19 by char
Translations of this page: