🚀 go-pugleaf

The point of using Prolog is to program at a "higher level" than is
possible with languages like C; that is, to write code which is more
closely related to the problem that you are trying to solve than to the
machine on which the program is to be run.

Pointers are a low-level concept.  The lack of pointers in Prolog is one of
its major advantages.  Since there are no pointers there are no dangling
pointers, and one major source of difficult-to-debug programming errors is
entirely eliminated.

I agree with you that using infinite structures in Prolog is more trouble
than its worth.  If the problem to be solved intrinsically requires a
complex data structure such as a cone, then I would suggest writing at
least part of your program in a language like C.  You may be able to have
the best of both worlds by defining the cone as an abstract data type in C,
and making all the operations on that data type available to Prolog.

The way that I would program your original example of a tree where each
node contains data about a person, and you want constant time access from a
person to his/her spouse, is to put all the data about the individuals into
the Prolog database.  Assuming that you have some good way of identifying
individuals (either by name or by some unique identifying number), and
assuming that your Prolog system gives you good (hash-table) indexing, you
can have essentially constant time access to any record.  You can then
build the tree with the nodes containing only the identifying numbers of
the persons, and look in the database whenever more information is needed.