Check out Glinski's Hexagonal Chess, our featured variant for May, 2024.

Enter Your Reply

The Comment You're Replying To
🕸Fergus Duniho wrote on Sat, Jan 7, 2017 02:50 AM UTC:

I have just created a new function called filter. Like aggregate, it takes a lambda function and an array as arguments, and it returns an array. Unlike aggregate, it returns both the key and the value of any array element for which the Lambda function evaluates as true, and it can use both the key and the value in the Lambda function. In the Lambda function, #0 stands for the key, #1 for the value. When the value is an array, #1 is the first element in the array, #2 the second, and so on. While aggregate returns the value of the Lambda function for each true call of it, filter just returns the key and value from the original array. So there is no need to include the return value in the Lambda function when using filter. So, you can ignore what I said in my last message and make these substitutions in your code:

Instead of onlyupper, use "filter lambda (isupper char #1 0) pieces"

Instead of onlylower, use "filter lambda (islower char #1 0) pieces"

If you use any piece labels that do not begin with an alphabetic character, these will work better:

Instead of onlyupper, use "filter lambda (fnmatch "*[A-Z]*" #1) pieces"

Instead of onlylower, use "filter lambda (fnmatch "*[a-z]*" #1) pieces"

I also created a regmatch function, which you can use if you are familiar with regular expressions. It works like fnmatch except that the first argument should be a regular expression instead of a wildcard pattern.

Instead of onlyupper, use "filter lambda (regmatch "/[A-Z]/" #1) pieces"

Instead of onlylower, use "filter lambda (regmatch "/[a-z]/" #1) pieces"

For the friend functions, you can use what I already gave you, or you can use one of these pairs:

fnmatch "*[A-Z]*" #0

fnmatch "*[a-z]*" #0

regmatch "/[A-Z]/" #0

regmatch "/[a-z]/" #0

 

 


Edit Form

Comment on the page How to Display Legal Moves in Game Courier - A Tutorial

Conduct Guidelines
This is a Chess variants website, not a general forum.
Please limit your comments to Chess variants or the operation of this site.
Keep this website a safe space for Chess variant hobbyists of all stripes.
Because we want people to feel comfortable here no matter what their political or religious beliefs might be, we ask you to avoid discussing politics, religion, or other controversial subjects here. No matter how passionately you feel about any of these subjects, just take it someplace else.
Quick Markdown Guide

By default, new comments may be entered as Markdown, simple markup syntax designed to be readable and not look like markup. Comments stored as Markdown will be converted to HTML by Parsedown before displaying them. This follows the Github Flavored Markdown Spec with support for Markdown Extra. For a good overview of Markdown in general, check out the Markdown Guide. Here is a quick comparison of some commonly used Markdown with the rendered result:

Top level header: <H1>

Block quote

Second paragraph in block quote

First Paragraph of response. Italics, bold, and bold italics.

Second Paragraph after blank line. Here is some HTML code mixed in with the Markdown, and here is the same <U>HTML code</U> enclosed by backticks.

Secondary Header: <H2>

  • Unordered list item
  • Second unordered list item
  • New unordered list
    • Nested list item

Third Level header <H3>

  1. An ordered list item.
  2. A second ordered list item with the same number.
  3. A third ordered list item.
Here is some preformatted text.
  This line begins with some indentation.
    This begins with even more indentation.
And this line has no indentation.

Alt text for a graphic image

A definition list
A list of terms, each with one or more definitions following it.
An HTML construct using the tags <DL>, <DT> and <DD>.
A term
Its definition after a colon.
A second definition.
A third definition.
Another term following a blank line
The definition of that term.