Documentation for the Behind operator #171
Conversation
bear8642
left a comment
bear8642
left a comment
There was a problem hiding this comment.
Typo in Behind.md, otherwise comments are mainly stylistic
windows-installation-and-configuration-guide/docs/interoperability.md
Outdated
Show resolved
Hide resolved
language-reference-guide/docs/primitive-operators/operator-syntax.md
Outdated
Show resolved
Hide resolved
language-reference-guide/docs/primitive-operators/operator-syntax.md
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
See my comment against this image in language-reference-guide/docs/primitive-operators/operator-syntax.md
Essentially, this diagram needs to match the other ones stylistically. Either redo this to match those, or update those to match the new one.
| Function composition refers to the "gluing" together of two functions using a dyadic operator such that the functions are applied to the argument(s) as normal, but in a particular pattern specific to the operator that is being used. The term function composition comes from traditional mathematics where it is used for a function `h(x)=f(g(x))` when written as `h(x)=(f∘g)(x)` APL generalises this idea to dyadic functions, allowing various patterns of application in addition to the simple application of one monadic function to the result of another monadic function. The three main patterns, represented by Atop, Beside, and Over can be visualised as follows: | ||
| Function composition refers to the "gluing" together of two functions using a dyadic operator such that the functions are applied to the argument(s) as normal, but in a particular pattern specific to the operator that is being used. The term function composition comes from traditional mathematics where it is used for a function `h(x)=f(g(x))` when written as `h(x)=(f∘g)(x)` APL generalises this idea to dyadic functions, allowing various patterns of application in addition to the simple application of one monadic function to the result of another monadic function. The four main patterns, represented by Atop, Behind, Beside, and Over can be visualised as follows: | ||
|
|
||
|  |
There was a problem hiding this comment.
This diagram needs to match the other ones stylistically. Either redo this to match those, or update those to match the new one! The four should also be presented in the same order as listed at the end of the previous paragraph (select the order that is most logical and then order the images and paragraph listing to match).
There was a problem hiding this comment.
This is not needed – it is not part of the work listed in the Mantis issue for this document, and has been superseded by a different approach. I will ask Stefan to confirm and delete any unnecessary files.
|
Does the documentation on missing glyps now mention the fact that if you use Link, and under the covers ⎕FIX and ⎕NGET (as I remember it) with the correct variant, the interpreter will store code using the Unicode glyphs but translate to the relevant ⎕xxxx names on the way in and out? If not, perhaps it is time to document that. |
The Function Composition section in the primitive-operators/operator-syntax page probably should have an updated image. I don't have the skills to make that image, so for now, I have added the diagram for Behind from the APL wiki.