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
|
# Enums should be able to store structs as well
struct EnumTester {
int i, j
~EnumTester ptr
}
# Simple integer enum
enum IntEnum [int] {
A = 0,
B = 1,
C = -2
}
# Simple float enum
enum FloatEnum[float] {
A = 0.1,
B = 0.2,
C = 3.1415
}
# More complex struct enum
enum TestEnum [EnumTester] {
A = {1, 2, null},
B = {2, 3, ~TestEnum.A},
C = {3, 3, null}
}
# Type enum
enum TypeEnum [type] {
A = int,
B = float,
C = EnumTester
}
enum SurfaceType [int] {
LAND = 0,
WATER = 1,
AIR = 2,
SPACE = -1
}
/; interface Vehicle
/; fuel [float] ;/
/; max_speed [float] ;/
/; min_speed [float] ;/
/; can_travel (SurfaceType surface) [bool] ;/
;/
struct Car extends Vehicle {
int wheels
}
struct Boat extends Vehicle {
int propellers
}
struct Plane extends Vehicle {
bool biplane, passenger
int engines,
}
struct Rocket extends Vehicle {
int
engines,
stages
}
struct HoverCraft extends Vehicle {
{3}float
max_antigrav,
bool
space_ready
}
# Enums can also handle interfaces (and extended types)
# but only if the given standard library has support for those things
enum CommonVehicles [Vehicle] {
A = {4}[Car],
B = {1}[Boat],
C = {false, true, 2}[Plane],
D = {4, 5}[Rocket],
E = {{5, 14.8, 5}, false}[HoverCraft]
}
|
