Entropy - Inaccurate programming language

In the comments to a recent post about an inaccurate processor , the habraser lol2Fast4U cited a link to an interesting programming language - Entropy .

The essence of this language is that it lacks determinism.

Every time we refer to any data, they are distorted more and more.
')
It would seem that the meaning of the creation of this language is very doubtful. But in fact, this approach can be useful for emulating just the very inaccurate processors referred to in the above post.

You understand that the approach to programming in such an environment should be fundamentally different.

A language has only a few data types — real (number), char (character) and string (char array).

The standard “Hello World” will look like this:

Program MyNamespace MyProgram [ print "Hello, World"; ] 

But the result of the conclusions can be:

 Hello+ World 

or

 Hellp, World 

As a demonstration of the gradual destruction of data, we can give an example where in a cycle one bottle of beer is “drunk”:

 Program Rottytooth NinetyNineBottles [ declare count real; let count = 99; while count > 0 [ if count < 99 [ print count; print " bottles of beer on the wall.\n"; ] print count; print " bottles of beer on the wall, "; print count; print " bottles of beer.\nTake one down, pass it around, "; let count = count - 1; ] print " no more bottles of beer on the wall."; ] 

As a result, the output first looks like this:

 98.99005 bottles of beer on the wall, 98.86667 bottles of beer. Take one down, pass it around, 98.46358 bottles of beer on the wall. 98.39877 boutles of bedr nn the wall, 98.42226 bottles of beer. Take one down, pass it around, 97.4903 bottles of beer on the wall. 97.52608 boutles of bedr nn the wall, 97.45941 bottles of beer. Take one down, pass it around, 96.44245 bottles of beer on the wall. 96.4431 boutles of bedr nn the walj, 96.46104 bottles of beer. 

Then:

 66.13296 bptumfu og!bedq▼no sif xali*▼66.10684!alttlfs of bgerTake omf down+ pas s!it aroune, 65.0071 bnstles of bedr pm▼the waml/ 65.02724 bpttmfu of!bedq▼no sif xali*65.00817!alttlfs of bgerTake omf dowm+ pas r!it aroune, 64.02435 bnstles of bedr pm▼the waml/ 

And then comes to something unreadable:

 6804 ekttjes og!bdes qmvhf zbnl0♀13.03909 cnutlew!mi!afeq qp▼sie w`lk+←13.03666 amttmfv▼qg!bhfrUbkd omc!dpwn-!patv"gv!crswnf. 11.99166 ektsjes og!bdes qmvhf z anm0♀12.01574▼cnutlew!ni!afeq qp▼sie w`lk+←11.9922 amttmfv▼qg!bhfrUbkd okc!dpwn- !patv"gv!crswmf. 11.17373 ektsjes og!bdes qmvhf zanm0♀11.18238▼cnutlew!ni!afeq qp▼sie w`lk+←11.27068 amttmfv▼qg!bhfrUbkd okc!dpwn-!patv"gv!crswmf. 10.02247 ekt sjes og!bdes qmvhf zaom0♀10.22528 cnutlew!ni!afeq qp▼sie w`lk+←10 

This example clearly shows how the data is gradually destroyed. And, therefore, the programmer needs to think about accessing the data as little as possible.

I don’t know how close it is to what is happening in the aforementioned inaccurate processor, but the essence is clear. And this illustration clarifies in general the principles of inaccurate programming. And then, judging by the comments to the previous post, many do not even know how a processor can be non-deterministic inaccurate.

As a bonus, you can play with a chat bot written in Entropy: Drunk Eliza .