08-17-2020, 07:48 AM
(This post was last modified: 08-17-2020, 08:09 AM by dale walton.
Edit Reason: Attached game progress - nearly there,but can't quite get it to work yet
)
Also having problems with nested (do ... or do within an (or.. list of moves.
I am about 3 bugs away from a viable game. - Options to come later - see attached.
Then I thought I might be having a problem with modifying the (to) part of the implied move, so tried using do to apply it using an ifAfterwards move filter.. I don't know which way works fastest or best, but my 1.0.3 is not yet compiling it and I don't see the reasons. - and also am not sure if the ifAfterwards should take to, from or last To, last From.
I am about 3 bugs away from a viable game. - Options to come later - see attached.
(08-17-2020, 07:47 AM)Eric Piette Wrote: (bySite) is the previous name of the ludeme (forEach Site ....). We just did not update the documentation for (site) but the ludeme (site) can be used to iterate the sites got by (forEach Site ...)Not sure why it didn't work for me, so I changed the algorithm to do it on the fly without states.
I have now updated the documentation, that will be published with the next release.
So the description you posted here is correct and works (I just test it).
Regards,
Eric
Then I thought I might be having a problem with modifying the (to) part of the implied move, so tried using do to apply it using an ifAfterwards move filter.. I don't know which way works fastest or best, but my 1.0.3 is not yet compiling it and I don't see the reasons. - and also am not sure if the ifAfterwards should take to, from or last To, last From.