Improving Readability of Code

[ghost]

I thought a readability improvement idea, ex.:
[5 6 -] [4 [1 2 +] *]
We could use non-code elements(escapeable elements) like [] to tell users what is going on code.

[h3rald]

😳

Hmmm... I can't understand that, sorry... also > and < are used in (system) symbols and sigils

[ghost]

Maybe we should use different symbols for the concept ??
~~ ^^ etc.

[h3rald]

Yes definitely... ^ is for lambda and ~ will probably become lambda-bind. Ideally I'd use only one character, better if matching like brackets but I could live with just one character... which though...

Maybe , or _?

; Your proposal:
[5 6 -] [1 2 +] [4 [1 2 +] *]

; Another possibility:
,5 6 -, ,1 2 +, ,4 ,1 2 +, *,

; And another:
|5 6 -| |1 2 +| |4 |1 2 +| *|

Your proposal is definitely more readable. I am going to give it some serious thought. Also instead of not doing anything we could add additional checks, for example:

• [-- start recording
• 5 -- one value added
• 6 -- another value added
• - -- symbol pushed on the stack
• ] -- verify that all symbols from the last [ have been consumed (*)

(*) Not sure how to implement this, because values have already been consumed by -.

I'd just like to use those symbols for something, you know?

[ghost]

[-- start recording
5 -- one value added
6 -- another value added

• -- symbol pushed on the stack
  ] -- verify that all symbols from the last [ have been consumed (*)

###Min###########
# Achievement get! #
# More dicipline. #
#############

I'd just like to use those symbols for something, you know?

I didn't understand but if you want to use them at special areas then i may think what would be use cases of them.

[h3rald]

Yes, I would like them to do something, and something important... not getting ignored. Maybe I can find a way to monitor stack popping and keep track of what gets popped between a [ and a ], handling nesting of course...

[h3rald]

I was thinking about this again and I am not sure: those brackets do complicate min code a lot. And one of the (weird) good things about concatenative languages is that you shouldn't need to use brackets or parenthesis to clarify precedence.

Putting this on hold for now.