Update (It's not dead)

I am going to be adding that along with several more functions. Also, I didn't mention this in the video but I am going to be adding an updated version of 2.0.8 as soon as I get it compiled. I am releasing a new installer for linux which should work with any distro that uses apt. The update is using the latest versions of the dependency libraries.

Just did a quick thought about above combining it with deepnes attribute similar to a dimensional attribute of arrays.

Array two dimensional is a field with a[2][2] having a[0][0] = 1, a[0][1] = 2, a[1][0] = 3 and a[1][1] = 4 members, an adjective b[2][2] with deepness 2, has 2 types with totally 4 subtypes.

Difference is that setting all members of a[2][2] the same means that comparations between different members will lead to true.


a[0][0] =1
a[0][1] = 1
a[1][0] =1
a[1][1] = 1

if (a[0][0] = a[1][1]) then
fprint("true")
else
fprint("false")
end if


prints true

on  the other side adj b with all subtype being the same



set int b[0][0] =1
set int b[0][1] = 1
set int b[1][0] =1
set int b[1][1] = 1

if (b[0][0] = b[1][1]) then
fprint("true")
else
fprint("false")
end if
would print false.

Okay a function to get the value of a subtype of a adjective is a idea here, but then this would also not hand a true as for example a function called data() and a function called mag() as in magnitute

set int b[0][0] =1
set int b[0][1] = 1
set int b[1][0] =1
set int b[1][1] = 1

if (data(b[0][0]) = data(b[1][1])) then
'with data(b[0][0]) gives 0 and data(b[1][1]) gives 3'
fprint("true")
else
fprint("false")
end if
'prints false'

if (mag(b[0][0]) = mag(b[1][1])) then
'with mag(b[0][0]) gives 1 and mag(b[1][1]) gives 1'
fprint("true")
else
fprint("false")
end if
'prints true'


compared to dim() would be dpn() (as in deepnes) and compared to size() would be amt() (as in ammout)
with dpn(b) returns 2
with amt(b,2) returns 2

Compared to array this has the advantage of members being distinctive and the disadvantage of coming with a lot more typing work compared to arrays.
It could be used to quickly set up a turing machine adding to numbers in RCBasic:


adj TuringMachine[4]
set str TuringMachine[0]= "add"
set str TuringMachine[1]= "5"
set str TuringMachine[2]= "4"
set str TuringMachine[3]= "outcome"


TuringMachine MachineState! = TuringMachine[0]



With val(mag(MachineState!)) following code does the same as 4 +5 and prints 9:

x = 0
while(MachineState! != TuringMachine:"outcome")
for i = 0 to 3
MachineState! = TuringMachine[î]
if(val(mag(MachineState!)) =0)then
if(MachineState! = TuringMachine:"ADD") then
if(val(mag(MachineState!)) != 0) then
x = x + val(mag(MachineState!))
end if
end if
end if
next
wend
fprint(x)
waitkey()


How do you plan to introduce matrices or matrix math?

be aware that m3 = m1*m2
while m4 = m2*m1

multiplication is not communative or how its called in math terms.

you had to assert a lot of stuff or go with functions that can dynamical allocate or say a matrix member is a 'can be filled but initialized with zeros' position.

at least this is what i would consider first as solution.

what would be nice as structural addition is geometrical vectors as structures that can be called as a whole, added as a whole initialized through a function that takes 1,2 or 3 arguments or with their sub members array like as
vector[x] or vector[y] or vector [z].

well would be nice for readability