APL Orchard: Difference between revisions

Jump to navigation Jump to search
37 bytes added ,  14:49, 20 November 2019
m
7 revisions imported: Migrate from miraheze
Miraheze>Adám Brudzewsky
m (Text replacement - "<code>" to "<source lang=apl inline>")
m (7 revisions imported: Migrate from miraheze)
(3 intermediate revisions by 2 users not shown)
Line 1: Line 1:
The APL Orchard is a Stack Exchange chat room dedicated to learn and teach APL, and to ask and answer questions about both golfing and general coding in APL. It began on January 24, 2017, and remains the most active APL chat room today.
The APL Orchard is a Stack Exchange chat room dedicated to learn and teach APL, and to ask and answer questions about both golfing and general coding in APL. It began on January 24, 2017, and remains the most active APL chat room today.


From October 18, 2017 until May 16 2018, Adám Brudzewsky ran a series of 29 live 90-minute study sessions which became known as ''APL Cultivation''. They cover most aspects of basic APL programming. Transcripts are available (see [[#External links]]).
From October 18, 2017 until May 16 2018, Adám Brudzewsky ran a series of 29 live 90-minute study sessions which became known as ''APL Cultivation''. They cover most aspects of basic APL programming. [[#External_links|Transcripts are available]].


=== Chat bot ===
=== Chat bot ===


The room features a chat bot which can evaluate single lines of APL. To use it, prefixed a chat message by <source lang=apl inline>⍞←</code>. Use <source lang=apl inline>⎕←</code> instead for boxed display and multi-line results and use <source lang=apl inline>⋄</code> instead to silence the first statement, after which subsequent statements must use <source lang=apl inline>⎕←</code> to output. Use <source lang=apl inline>]</code> to prefix user commands (without <source lang=apl inline>⎕←</code> or <source lang=apl inline>⍞←</code>), including e.g. <source lang=apl inline>]help ⍣</code> for help on the <source lang=apl inline>⍣</code> glyph etc. Do not use markdown, but fixed-width (4 or more initial spaces, which can be inserted by pressing <kbd>Ctrl</kbd>+<kbd>K</kbd>) is fine. This also ensures proper rendering with monospace font and avoids interpretation of APL symbols as markdown.
The room features a chat bot which can evaluate single lines of APL. To use it, prefixed a chat message by <source lang=apl inline>⍞←</source>. Use <source lang=apl inline>⎕←</source> instead for boxed display and multi-line results and use <source lang=apl inline>⋄</source> instead to silence the first statement, after which subsequent statements must use <source lang=apl inline>⎕←</source> to output. Use <source lang=apl inline>]</source> to prefix user commands (without <source lang=apl inline>⎕←</source> or <source lang=apl inline>⍞←</source>), including e.g. <source lang=apl inline>]help ⍣</source> for help on the <source lang=apl inline>⍣</source> glyph etc. Do not use markdown, but fixed-width (4 or more initial spaces, which can be inserted by pressing <kbd>Ctrl</kbd>+<kbd>K</kbd>) is fine. This also ensures proper rendering with monospace font and avoids interpretation of APL symbols as markdown.


Only a few special [[system commands]] are available: <source lang=apl inline>)lb</code> for language bar, </code>)docs</code> for full documentation, <source lang=apl inline>)ref</code> for a link to the PDF reference card, <source lang=apl inline>)idioms</code> for a link to a searchable [[idiom|idiomatic expressions]] list.
Only a few special [[system command]]s are available: <source lang=apl inline>)lb</source> for language bar, <source lang=apl inline>)docs</source> for full documentation, <source lang=apl inline>)ref</source> for a link to the PDF reference card, <source lang=apl inline>)idioms</source> for a link to a searchable [[idiom|idiomatic expressions]] list.


=== Access ===
=== Access ===

Navigation menu