xpqz / cultivations Goto Github PK

It'd also be nice to show the "head and tail" trick:

      1 1⊂'Hello'
┌→───────────┐
│ ┌→┐ ┌→───┐ │
│ │H│ │ello│ │
│ └─┘ └────┘ │
└∊───────────┘

You need to read the first three lines and the last three lines separately.

Instead, split into two code blocks.

Now you can see

that the first a is labeled

"a" should be "`a`" (code).

?S

Needs a space

Maybe a note about ability to see this as a video at https://dyalog.tv/Webinar/?v=6SAsgEvUmkU

a .NET collection example for monadic ⌷:

      ⎕USING←'System.Collections'
      ba←⎕NEW BitArray(⊂1 0 1 1 0)
      ba
System.Collections.BitArray
      ⌷ba
1 0 1 1 0

Note: doesn't seem to work on MacOS.

This example does not look correct. The second result should be 1 2 3 4. The reason is that the assignment of ⎕IO should precede ⍳4.

⍳4
⎕IO←0
⍳4
⎕IO←1
0 1 2 3
0 1 2 3

@abrudz says:

I think the flow will be easier to understand if the "We can model ⊥ as:" has reversed left arguments and does ⌽×\⌽

Maybe even revise everything from the beginning to do ⌽×\⌽ throughout, i.e. ⌽×\⌽(2⍴10),1 etc.
And again, ×\⌽1 1 1 is wrong. It should be ⌽×\⌽1 1 1
And harmonise ⌽×\1,⌽1↓0 0 0 to ⌽×\⌽1↓0 0 0,1

MathJax mess-up after "Compare this to making cash change: there’s nothing larger than a"

Hm, now I look at ⊤ maybe the formulation ⌽×\⌽1,⍨1↓ is best, as it puts all transformation on the left, keeping the base on the right?

@abrudz says:

• ¯1⎕C⎕A can be just ⎕C⎕A.
• "the first feels more natural to Windows users while the second feels more natural to UNIX users" is exactly backwards
• f1 → <kbd>F1</kbd>
• ⍕ returns a vector for single line arguments, and a matrix otherwise." isn't actually true. ⍕ keeps the rank of its argument (except for numeric scalars becoming character vectors).
• "convert an---d--- APL string".
• End of ⎕JSON could mention the option to use ⎕NULL
• there could be a sentence about JSON5 too.

@abrudz says

"Since APL does not enforce a naming scheme" … (but I highly recommend adopting a naming scheme)

"of dfns' operators" → "the dfns workspace's operators"
"[workspace available]" broken link
I'd remove mention of ⎕Á as it makes little sense, and it isn't even true that it is the list of non-ASCII identifier letters.
"⎕S can also take a scalar integer as right operand." → "⎕S can also take an integer scalar or vector as right operand."
⍠ missing backticks.
For counting uppercase letters, you could add ≢'\p{Lu}' ⎕S 0 ⊢ 'Programming Puzzles and Code Golf' ⍝ Unicode uppercase letter property

book.pdf

Created a PDF of the entire book for download if people need it.

@abrudz says:

• 1=1+1e¯20 should be 1e¯15
• at the end of ⎕PP you should set it back to 10.
• ⎕RL treatment needs a bit of changing as the default is ⍬1 (I was speaking about the then-bot).
• ⎕TS should at least mention ⎕DT.

]?

The modern (more consistent) syntax is ] -?

]CD is also able to change current directory — cross platform.

]DInput is kind of obsolete in light of the experimental multi-line input mode.

that alloweds you

I would move the "The command processor" section up to the intro.

]ADoc

Here’s some example code for that.

Also see the cultivation on plotting.

]FnsLike ]ObsLike

These are obsolete to ]names

usually adds more

There should be a non-Boolean ⍺ example.

This needs mention of the (new) fact that the left argument to ⊂ can be abbreviated, with missing elements presumed 0, and maybe an example of converting begin-points to mask:

      ⍸⍣¯1⊢1 5 10
1 0 0 0 1 0 0 0 0 1
      (⍸⍣¯1⊢1 5 10)⊂⎕A
┌→───────────────────────────────────┐
│ ┌→───┐ ┌→────┐ ┌→────────────────┐ │
│ │ABCD│ │EFGHI│ │JKLMNOPQRSTUVWXYZ│ │
│ └────┘ └─────┘ └─────────────────┘ │
└∊───────────────────────────────────┘

https://xpqz.github.io/cultivations/PDI.html:

will be paired up thewith the label