Implementing GoL as three plain shift registers with no previous/next-state memory causes discontinuities at row and field boundaries.
For row boundaries, the new cells coming in for the shift registers are off by one row. In order to handle this discontinuity, there would need to be some means of indexing data from the upcoming row, and swapping that data in when on a row boundary.
For field boundaries, the cell regions use a mix of current-generation data and next-generation data. Typically, a GoL implementation stores two generations of data and swaps between the display/working memory at the end of each field.
In this example image, green indicates the current cell being processed, black indicates current-generation neighboring cells, and red indicates next-generation neighboring cells.
Implementing GoL as three plain shift registers with no previous/next-state memory causes discontinuities at row and field boundaries.
For row boundaries, the new cells coming in for the shift registers are off by one row. In order to handle this discontinuity, there would need to be some means of indexing data from the upcoming row, and swapping that data in when on a row boundary.
For field boundaries, the cell regions use a mix of current-generation data and next-generation data. Typically, a GoL implementation stores two generations of data and swaps between the display/working memory at the end of each field.
In this example image, green indicates the current cell being processed, black indicates current-generation neighboring cells, and red indicates next-generation neighboring cells.