concurrent design for check

[ssqq]

[rickyboy]

Can you give details about what you're trying to do? What you are describing could be almost anything.

The basic idea is that, if you can't avoid the `do-some-thing` procedure being non-functional, then you hope that, at least, it frobs a variable that you can see in your caller; then, you can just check that. A general example of this setup is checking for EOF when in a loop reading from a file.

But if you can avoid such a situation, it's better to design something functional.

[TedWalther]

What do you mean by "functional". Goroutines? channels? slots? shared memory? NewLISP has built in "send" and "receive" functions... maybe that does with ssqq wants?

[rickyboy]

[ssqq]

I design a function model to implement "return" from any depth block.

in general, when call (return sth) in function, current function namespace would find a return value have been ready.

when return expression is in deep block, return message would be receive by main process after serval value pass.

If I use concurrent, send a message to main process, then is simply.

But send message directly to main process would destroy block stack management, if return expression is at last expression of function, restore some management variable is too waste time.

So i think, order compute is better than concurent compute in this function module.

[TedWalther]