I just wanted to say THANKS for such an interesting mingle-mangle of odd but nonetheless fascinating ideas! Please keep on going, new programming worlds want to be explored!

Best regards,
Andreas

For your code sample, the current public release would print “hello world” (I was trying to make it friendly) and the current unreleased version would print “helloworld” (trying to be accurate). An interaction like that with multiple strings means that each string is essentially packed into an argument list in the order it was read. Which is why “hello” comes first.

Really, I know you used venn diagrams earlier, I find myself slipping and thinking of everything as sets.

I take it your EOL terminated?

How does something like this work:
“hello” print “world”

would it be
hello
world
or
world
hello
or
hello world

?

Yes, you can impose order. Wheeler evaluates expressions as it sees them. Typically you’ll define a transition with an expression, then later another expression will trigger that transition. To reprint the hello world message, you just feed Wheeler that expression (print “Hello, world!”) again. The transition for printing is entirely repeatable. Other transitions may behave differently.

Passing around an association (I call them relations) is something I’ve gone back and forth about. I worked very hard to keep explicit variables out of the language, so having some kind of mechanism to capture a value by name feels dirty. But I’m considering it. For now you have to very explicitly state what you want, every time you want it.

But what then? Can I impose some sort of order on this? once I’ve created this association can I pass it around? Can I reprint the hello world message?

Just full of questions about this