Inherit block variables

[cookieclickerer33]

This suggestion is to make a block to inherit block variables from another block, possibly being a new function
[scratchblocks]
( variables from ({move::motion}::ring) ::grey
[/scratchblocks]
This would report a list of each block variable’s value in order
This would give more use to block variables by allowing different custom blocks to communicate with eachother

[joecooldoo]

i think this has been requested before, and I think its on the list of things they want to do

[bh]

You can fake it with message passing:

See Chapter VIII of the manual.

[cookieclickerer33]

But that’s not the same exactly as it interferes with messages

What if you send a message before the next call?
Or send a message named block variables, it’s not air tight

[bh]

@cookieclickerer33

What if you send a message before the next call?

I don't understand the problem. Every call would be a message passing in this approach. Could you explain in more detail?

@cookieclickerer33

Or send a message named block variables, it’s not air tight

Right, it's a workaround. I was imagining you using it yourself. If you're contemplating a library for general use, I would use a different message text, e.g., " block variables."