Andrew Lentvorski wrote: > The big problem is that time is a variable in our systems, *and we > don't account for it*. In spite of its best efforts, asynchronous > logic *still* hasn't made significant penetration into VLSI design > because it suffers from all the same problems that software does. > Consequently, everybody in VLSI still pretty much relies on a global > clock to lock everything together. If you look at how concurrency is handled in Erlang and Haskell, you'll have a better understanding of how managing "state" and managing "time" are really two sides of the same coin. Time only matters when there are changes of state.
--Chris -- [email protected] http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-lpsg
