# "Hexlife" in SWI Prolog — critique very much welcome!

**URL:** <https://swi-prolog.discourse.group/t/hexlife-in-swi-prolog-critique-very-much-welcome/4665>\
**Category:** General\
**Created:** [November 18, 2021, 7:11pm UTC](https://swi-prolog.discourse.group/t/hexlife-in-swi-prolog-critique-very-much-welcome/4665 "2021-11-18T19:11:00Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![EricGT](https://avatars.discourse-cdn.com/v4/letter/e/f1d935/32.png) [@EricGT](https://swi-prolog.discourse.group/u/EricGT)\
**Post date:** [November 18, 2021, 9:48pm UTC](https://swi-prolog.discourse.group/t/hexlife-in-swi-prolog-critique-very-much-welcome/4665/2 "2021-11-18T21:48:50Z")

</div>

Two things I might try if this were my problem.

1. concurrent\_forall/3 ([ref](https://swi-prolog.discourse.group/t/building-a-port-scanner/2580/28))
2. arg/3 - For a practical and simple usage of arg/3 see dynamic array ([code](https://swi-prolog.discourse.group/t/does-swi-prolog-have-n-k-trees/1310/5)) ([ref](https://swi-prolog.discourse.group/t/does-swi-prolog-have-n-k-trees/1310/6))

---

_[View the full topic](https://swi-prolog.discourse.group/t/hexlife-in-swi-prolog-critique-very-much-welcome/4665)._