It does, if the concurrency is to be transparent. Yes, you can add extra syntax and mutexes that allow the programmer to indicate that two or more separate statements may be overlapped--but why if you can do it without?
Extra syntax introduces extra level of lexical scoping--possible closures. I looked at this a few days ago. What happens when two threads attempt to access the same closure passed in from a level above them?
In reply to Re^26: Why is the execution order of subexpressions undefined?
by BrowserUk
in thread Why is the execution order of subexpressions undefined?
by BrowserUk
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |