I'm not sure I get your point. With your example you have kept the ".start()" parts. But with par there is no need for them any more. So the par vs bla.start seems about quits in terms of syntactic overhead and uglyness.
In the days of OCCAM one would could have parallel execution of statements that are not function calls:
Code: Select all
par
a = some_expression
b = some_expression
as opposed to sequential execution of statements.
Code: Select all
seq
a = some_expression
b = some_expression
Excuse the syntax which is probably not quite right, my memory of OCCAM is fading.
So here "par" and "seq" are essential.
Now assuming we can have "par" without the "on stdcore" stuff then "par" is still required to differentiate from sequential calls.
I have to get home and fire up my XDE to check this out.
P.S. Is it not so that the ".start()" business only comes about when you have an object oriented language with threads where you need to have a method (start()) to run on the thread differentiated from all the other objects methods.