02-16-2021, 06:57 AM
(This post was last modified: 02-16-2021, 09:22 AM by dale walton.
Edit Reason: Found the source of my problem, incomplete documentation.
)
I am getting compiler rejections when I try to use this new (directions ...) Ludeme, can you show an example of how it works?
Is it an array of Integers, or a list of strings? Can it be converted to a single item?
I had assumed you would give a less general (direction ...) function giving a single value, that could be then inserted to specify a direction value wherever such a value is allowed:
(move Step
(move Slide
(move Shoot
(move Hop
(custodial
(directionCapture
...
(sites Around
(sites Direction
(forEach Direction
(remember Value
(set Direction
Perhaps it already can do what I want, but the compiler hasn't been given the "OK" to allow it?
------------------------------------------------
OK, Looked again, and now understand a little better how it works. The problem was that one still needs "Adjacent" - I had assumed that the new function replaced the <directions> (which is optional in most the ludemes) but it turns out you need both.
That is a lot of documentation update needed...
---------------------------------------
PS I waste a lot of time everytime I switch code from (sites Around to Sites Distance to sites Direction because these unnecesarily require the same information in different sequences and formats. It is a general problem in other parts of the language as well which means having to refer continuously to documentation even when aware of the problem.
Is it an array of Integers, or a list of strings? Can it be converted to a single item?
I had assumed you would give a less general (direction ...) function giving a single value, that could be then inserted to specify a direction value wherever such a value is allowed:
(move Step
(move Slide
(move Shoot
(move Hop
(custodial
(directionCapture
...
(sites Around
(sites Direction
(forEach Direction
(remember Value
(set Direction
Perhaps it already can do what I want, but the compiler hasn't been given the "OK" to allow it?
------------------------------------------------
OK, Looked again, and now understand a little better how it works. The problem was that one still needs "Adjacent" - I had assumed that the new function replaced the <directions> (which is optional in most the ludemes) but it turns out you need both.
That is a lot of documentation update needed...
---------------------------------------
PS I waste a lot of time everytime I switch code from (sites Around to Sites Distance to sites Direction because these unnecesarily require the same information in different sequences and formats. It is a general problem in other parts of the language as well which means having to refer continuously to documentation even when aware of the problem.