I think using multi thread can use 0 but the =% and will stall if you dont use the jump. If you use a modular for the conversion and {[]} to compile you can cut the double back and forth the %= will convert using 4 or 7 for the thread and use a partion for the compiled.(kernal,cluster,orwhatever) Mult. Thread uses hologram or bit coin. You want to stay out of the 2 or 9 that will knock it into imput or output. To much distro or not enough.
I'm not sure where people even got the idea that volatile was useful for multi-threading - the only place I've ever seen it used was with memory-mapped hardware (described in the article as "memory modified by an external agent").
2 comments
0 u/Guyyepguy 15 Jul 2015 02:01
I think using multi thread can use 0 but the =% and will stall if you dont use the jump. If you use a modular for the conversion and {[]} to compile you can cut the double back and forth the %= will convert using 4 or 7 for the thread and use a partion for the compiled.(kernal,cluster,orwhatever) Mult. Thread uses hologram or bit coin. You want to stay out of the 2 or 9 that will knock it into imput or output. To much distro or not enough.
0 u/rdnetto 15 Jul 2015 17:17
I'm not sure where people even got the idea that volatile was useful for multi-threading - the only place I've ever seen it used was with memory-mapped hardware (described in the article as "memory modified by an external agent").