Are you starting a local or remote interpreter? Have you tried starting the interpreter first, and then connecting to it? Which versions of RIDE and Dyalog are you using?
@Adám Ah, I set that when it was just "APL*PLUS". So yes, now that II and III are split, only III should have control structures.
Might make sense to drop both II and III from the table on the grounds that APL+Win is clearly a continuation of that line. With two rows less the table certainly feels a lot more readable.
⍝ Can I save my funtion in a file mylib.txt and load it into RIDE?
fun ← {⍺ + ⍵}
⍝ I know I can save workspace )svae /tmp/ws.dyalog and )load /tmp/ws.dyalog
the problem is workspace file is binary file, it is impossible to edit it outside the RIDE
@1234 Yes, absolutely, and what we recommend too. Either you can do 2⎕FIX'file:///tmp/mylib.txt' or you can automate that whole process by entering ]create # /tmp which will load all .aplf, .aplo, .apln, .aplc, .apli, .apla files from /tmp and will synchronise changes when files or workspace are modified.
@RubenVerg Only uppercase E. However, it also supports entirely case-insensitive 0x1234 for hexadecimal input of integers (and floats if given more than 8 digits after x or X) and 0r1234 for (even small) floats, and 0b1010 for binary input of numbers.
@RubenVerg They just confusingly call ⊃ "Disclose".
@RubenVerg Maybe "support for all (?) APL dialects" should be qualified to be just the "nested" lineage (to exclude SHARP APL and A+)?
@Adám I won’t be able to join the Quest tomorrow. I can share my contribution from the last year competition but don’t know how to open .aplf files outside the Dyalog interpreter. But my solution wasn’t very special and rather straightforward.
@Richard go ahead. .aplf files are plain text files, so any text editor will do. On Windows, there's also our own stand-alone text editor that .aplf files should open in automatically.
