On Mon, Jan 17, 2011 at 1:44 AM, Wolfgang Jeltsch
Am Sonntag, den 16.01.2011, 14:48 -0800 schrieb gutti:
Looking at life u probably could save time, if u only would evaluate code on cells, where the neighbors have changed status. So rather than triggering them all centrally and each checks its neighbours, we could use the concept:
- let the active ones trigger the neighbours & so pass on activity
But then you would have to take care to avoid cycles. You could also use on-demand updates with a centralized approach, and a centralized approach would probably make cycle detection easier.
Don't forget about the double buffering you will need to do if you have a simultaneous rule. It doesn't take long before the dragons in imperative programming start messing with your "easy" specification.