index<--

EVE Data Types

Let's describe the basic types:

Bookmarks

• Primitive Types
• Single character
• Composite
• Data coercion
• Type inference
• Default types
• Logical type
• Gradual typing
• Calendar date
• Time duration

Primitive Types

Numeric Types

In EVE we can have two categories of numbers:

Discrete numbers:

For conversion into characters:

• The number of characters required for Integer numbers is 20. (19+sign)
• For Double numbers, conversion into characters is controled by #precision directive

Continuous numbers

The type Double is represented using floating precision numbers.
Floating decimal numbers are most simply described by 3 Integers:

• s: a sign (0 or 1)
• c: a coefficient
• n: an exponent

The numerical value of a finite number is −1ˢ × c × 2ⁿ Using this formula EVE define two floating point types.

Single: is single-precision 32-bit IEEE 754:
Double is double-precision 64-bit IEEE 754:

Precision is variable depending on the size of the number. The number of digits represents the largest number that can be converted from string format into a Double and back without loosing any digit. Think of it like a digital display from a packet calculator.

Numeric literals

Example:

#numeric literals
driver numeric_literals:

globals
    Integer i; // Initial value = 0
    Natural n; // Initial value = 0
    Double  r; // Initial value = 0.00

process  
    i := 9223372036854775807;  //  maximum
    n := 18446744073709551615; //  maximum
    r := 1/2; //  0.5
return;

See also: scientific notation

Single Character

Composite Types

Range

A range is a notation that can create a sub-set of integer numbers.

Syntax:

range ::= (min..max:ratio);

Notes:

• Limits are included by default,
• Upper or lower limits can be excluded using "!" instead of "."
• Range notation can be open at one end or both ends.

Example:

Numeric ranges:

#numeric range demo
driver numeric_range:
process
  print (0..5);    // (0,1,2,3,4,5)
  print (0.!5);    // (0,1,2,3,4)
  print (0!.5);    // (1,2,3,4,5)
  print (0..10:2); // (0,2,4,6,8,10)

  ** test range  
  expect 0 in (0..5); 
  expect 5 in (0..5); 
  ** test limits
  expect 0 not in (0!.5);     
  expect 5 not in (0.!5);   
return;

Example:

Symbol ranges:

# using symbol ranges
driver symbol_range:
process 
  print ('0'..'5') // ('0','1','2','3','4','5')

  ** following statements should pass
  expect ('0' in ('0'..'9'));  //will pass   
  expect ('X' in ('A'..'Z'));  //will pass
return;  

Notes:

• The implicit ratio is 1 and is optional
• Ratio cam be integer or decimal number

Domain

domain ::= [min..max] <: Super_Type

# domain demo
driver domain_demo:  
process 
    print [0..1]; // [0..1]
    
    ** using domain
    expect 0   in [0..1]; 
    expect 1   in [0..1]; 
    expect 0.5 in [0..1];     

    ** exclude limits
    expect 0 not in [0!.1];
    expect 1 not in [0.!1];  
    expect 0.5 in [0!!1];
return;    

Data Coercion

In computer science coercion is used to implicitly or explicitly change an entity of one data type into another of different type. This is ready to take advantage of type hierarchies and type representations. If not designed properly the coercion can be a fatal mistake. EVE is a safe language so we do only safe coercion.

Implicit coercion In EVE the arithmetic operators are polymorphic. Numeric operators can do implicit data conversion to accommodate the data types and return an accurate result. Automatic conversion is possible only when there is no risk of loosing data precision. If there is a loss of precision we can end-up with a run-time error. To prevent this EVE will implement a safe compile-time check.

Notes:

• Implicit conversion is possible and safe :
• Explicit conversion is possible but unsafe :

#example of implicit conversion
driver implicit_coercion:

globals
  Integer a = 2;
  Double  b = 1.5; 
  
process
  b := a;       //  this implicit cast is possible b = 2.0
  b := a + 3.5; //  add 3.5 then assign result to b = 5.5
  a := b;       //  error: can not assign Double to  Integer
  a := 1.5;     //  error: can not assign Double to  Integer
return;

Explicit coercion Explicit coercion is a forced conversion. Can be used to convert backwards from higher data range to lower data range or from continuous numbers to discrete numbers. This however can cause a data or precision loss. Explicit coercion is using a function.

Examples of explicit coercion:

# explicit coercion in EVE
driver explicit_coercion:

globals
  Integer a = 0;
  Double  b = 1.5;

process
**explicit coercion lose (0.5)
  a := floor(b);
  write  a; //will print: 1
 
**explicit coercion add (0.5)
  a := ceiling(b); 
  print  a; //will print: 2

**explicit coercion rounding:  
  a := round(b);
  print  a; //  will print: 2
return;

Number to a string

#convert number to string
driver number_to_string:

global
  String  s; 
  Integer v = 1000;
process
  s := format(v); //  explicit coercion s = '1000'
  expect s == a'1000'
return;

String to a number

This can be ready using the casting function parse(), only if the string contains a number. Otherwise the conversion fail and will rise and exception.

#string to number conversion
driver string_to_number:
globals
  Integer  v; 
  Double   b;
  String   s = '1000';
  String   r = '200.02';
process
  v := parse(s); //  make v = 1000
  v := parse(r); //  make v = 200 and decimal .02 is lost
  b := parse(r); //  make b = 200.02 and decimal .02 is preserved
return;

Note: Build-in functions that are located in EVE default library: { parse(), format(), ceiling(), floor() round()}. This module is one of the standard modules that are automatically included in any EVE program.

Type inference

This is a logical deduction of data type from constant literals.

Example:

#test type inference
driver type_inference:

** Define a list of 10 elements using type inference
global List ls = [0,1,2,3,4,5,6,7,8,9]; //  initialized list of Integer   

process
  print  ls.type(); //  List[Integer]
  expect ls is List[Integer];
return;

Default types

Literals are representations of specific particular data type in source code.

Basic types Next notation use "9" to show any digit in range [0..9].

Zero literals

Collection literals

Type Inference

Sometimes the type is partially specified to simplify type declaration:

# gradual type declaration
global
    ** member type is inferred later from first member
    List a := [];

Type verification

We can verify the type using "is" operator:

# using operator "is" to check type
driver type_check:

globals
    ** define object and initialize
    Object r = {name:"test", age:"24"};  
    ** define hash table
    Map    t = {('key1':"value1"),('ley2':"value2")}; 

process
    ** check variable types using introspection
    expect r.name  is Text;
    expect r.age   is Text;
    expect t.key   is String;
    expect t.value is Text;
return;

Printing type()

For type introspection we can use type() built-in function:

# introspection demo
driver print_type:

global  Double i = 1.5;
  
process
  expect i is Double;
  print "type of i is \s" ? type(i);
return;

Polymorphic operators

Logical type

In Latin the "falsus" and "verum" are translated in English to "false" and "true".

• falsus := ⊥ defined by ⊥ := ¬ ⊤ and ( P ∧ ¬P )
• verum := ⊤ defined by ⊤ := ¬ ⊥ and ( P ∨ ¬P )

Syntax:

Logic: name = False; // explicit initialization

Internal design

Probably best to define Logic type is Ordinal:

type Logic = { .False , .True } <: Ordinal;

Logical expressions

A logical expression is a demonstration or logical deduction having result True or False. Operator precedence is: {not, and, or, xor}. The order of operations can be controlled using operator precedence and round parentheses.

Result of logical expressions can be used into a conditional statement to make a decision. Also results of logical expressions can be stored in logical variables to be used later in other conditions.

Gradual typing

Gradual typing is a type system in which some variables may be given types and the correctness of the typing is checked at compile-time (which is static typing) and some variables may be left un-typed and eventual type errors are reported at run-time (which is dynamic typing). To declare gradual types we use a polymorphic type called variant.

Variant Types

A Variant is a polymorphic variable that can have multiple types but only one at a time:

Syntax:

** define variant subtype
type Variant_Name: {Type | Type | ... } <: Variant;

**  declare single variable (with initial value)
global Variant_Name v = value; 

Variant Properties

• Variant data type is assigned at runtime;
• One variant can have a single value at a time;
• One variant is a "union" of several types

Making a null-able type

For this we use a special type Null

• The Null type is a curious type;
• It can have only one value = Null;

Pattern:

** define nulable variant
type Number: {Integer | Double | Null} <: Variant;

** use nulable variant
global Number: x; // default value is Null

Usability

A variant can establish its data type at runtime:

Example 1:

In next example variant we use a variant that can be Double or Integer.

#variant type demo
driver variant_type:

globals
    Double | Integer v, x ,t;
    
process   
    ** safe conversion
    t := 1 / 2;   // make t Double    
    t := 12;      // change type
    print type(t) // Integer
    
    ** unsafe conversion
    x := 1.5;   //  x is Double    
    v := 1; //  v is  Integer    
    v := x; //  v becomes Double     
    print type(v) // Double
return;

Example 2:

A variant is a way to create a generic routine. For this we use variant parameters:

# variant parameter in routines
driver variant_params:

** define a subroutine that can swap two numbers
routine swap(Integer | Double x, y):
    Integer | Double i
process  
    expect type(x) = type(y);
    
    i := x; //  intermediate reference
    x := y; //  first  swap
    y := x; //  second swap
return;

globals
    Integer y;   // default zero
    Double a, b; // default zero
    
process  
    ** invert two  Integer numbers
    x := 10;
    y := 20;  
    swap(x, y);
    expect (x == 20) and (y == 10);
    ** invert two Double numbers
    a := 1.5;
    b := 2.5;
    swap(a, b);
    expect (a == 2.5) and (b == 1.5);
return;

Calendar date

In EVE we represent calendar date.

Date storage

• Date type is internally stored as number on 4 bytes;
• First byte store the day, second byte store the month;
• Last 2 bytes store the year;

Date literals

When can create a date literal using 3 format functions:

• ydm() format: "YYYY/DD/MM"
• dmy() format: "DD/MM/YYYY"
• ydm() format: "MM/DD/YYYY"

Note: A reversible function is overloaded.

#overloaded function
routine main:
    Date: date := "2019/01/30" as YDM
process
    print date as YDM; //  2019/01/30
    print date as DMY; //  30/01/2019
    print date as MDY; //  01/30/2019
return;

Time Duration

Time data type can be used to represent duration.

• EVE duration can represent minimum 1 millisecond.
• EVE duration can represent maximum 4294967296 hours.

Representation Time is represented as a number on 8 bytes.

• First 2 bytes are the milliseconds.
• Next 2 bytes are representing seconds and minutes.
• Last 4 bytes represents hours.

Conversion

Time format is created using two reversible functions: t12() and t24()

• T12 accept format ("hhhh:mm:ss,9999ms")
• T24 accept format ("hhhh:mm:ssxx, 9999ms" )

ss: can be 0..60 seconds
xx: can be: (am/pm)

Example:

# time demo
driver time_demo:
globals
    Time time1 = time2 = time3 = "00:00";
process
    time1 := "23:63" as T24;
    time2 := "23:63:59,99" as T24;
    time3 := "11:63:59pm,99ms" as T12;
return;

Read next: Collections