> Yes, many OS's suggest spinning up a worker thread, but by default an app is single-threaded. The default in BeOS is 2 threads.
It's an interesting idea. It would be trivial to write boilerplate like this so that when you create a new .c file, it will start with a basic multi-threaded application.
I remember seeing some parallel FORTRAN code in the late 80's with things like loops explicitly marked for parallel execution and other tricks. The downside is that debugging mutable state across multiple threads is a bitch. It's not something I would wish to my worst enemy.
> Look at Verilog/VHDL for an example of a fully parallelized language.
I have been playing with the idea of using Verilog or VHDL to express computer programs... Did nothing, but it would be an interesting thing to test.
It's an interesting idea. It would be trivial to write boilerplate like this so that when you create a new .c file, it will start with a basic multi-threaded application.
I remember seeing some parallel FORTRAN code in the late 80's with things like loops explicitly marked for parallel execution and other tricks. The downside is that debugging mutable state across multiple threads is a bitch. It's not something I would wish to my worst enemy.
> Look at Verilog/VHDL for an example of a fully parallelized language.
I have been playing with the idea of using Verilog or VHDL to express computer programs... Did nothing, but it would be an interesting thing to test.