Thanks,
Thanks,
Thanks,
"The differential equations that describe dynamic interactions of power generators are similar to that of the gravitational interplay among celestial bodies, which is chaotic in nature."
Call stack is area where CPU keep track of memory and instructions and all the program information needed to stay running. These could not be readily shared between two threads because that is the machine in actual operation.
it always seems to hang sooner or later or data gets corrupted or in one way or another something just does not work right.
Originally posted by Marco Ehrentreich:
It's probably better to give this a try instead of long discussions here
Funny explanation of multi-threading issues but it gets to the point. This "seems to hang" or "gets corrupted" errors are well-known issues when trying to execute non-thread-safe code with multiple threads. There are race conditions, data races, dead locks, visibility problems and and and... But that's not easy enough to explain here in a few words.
"The differential equations that describe dynamic interactions of power generators are similar to that of the gravitational interplay among celestial bodies, which is chaotic in nature."
Let that be our conclusive advice to original poster.
I was trying to achieve effectiveness in serving the poster's needs
Area of cpu? Ever seen the P-8 overlay? How about a 64x64 gated architecture running no-write-back Inventory Tracking and Control.
I knew that guy would be trouble! Thanks tiny ad!
a bit of art, as a gift, the permaculture playing cards
https://gardener-gift.com
|