« first day (2584 days earlier)      last day (53 days later) » 

12:00 AM
connect ECONNREFUSED ::1:4502
connect errro
 
Oh, sorry, I thought you were asking something very different.
Which OS are you on?
 
12:18 AM
Access error when starting interpreter executable
 
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?
 
12:38 AM
@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.
 
12:57 AM
⍝ 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
 
 
3 hours later…
 
1 hour later…
5:17 AM
@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.
 
 
4 hours later…
9:29 AM
is apl+win complex?
oh, also, does support vector arguments
is windowed reduce suported?
 
@RubenVerg No.
@RubenVerg No.
@RubenVerg No.
 
are ' and " for strings equivalent (both work like ' in other dialects) or is the second one a string with escapes, like in dzaima?
 
" is exactly like ' (as is the case in APLX)
 
9:45 AM
is first or mix?
oh, is listed as "first" so I guess is mix
is e/E notation for numbers supported?
what dialects support . for member access?
 
10:08 AM
@RubenVerg GNU, Dyalog, APL+Win, dzaima
 
dzaima has namespaces?
 
Basically. It has key–value maps.
 
ah, right, forgot about those
added apl+win to ominbar, as usual i'll have missed a bunch of stuff :)
(sorry for taking so long, busy with school stuff)
 
10:23 AM
@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+)?
 
why should I exclude those?
@Adám what does 0r do?
 
@RubenVerg Because otherwise you'll drown in glyphs and behaviours that are specific to those.
 
hmm, I'll think about it, seems weird not to (eventually) include those
 
@RubenVerg Inputs a float as hexadecimal representation of (a prefix of) its IEEE 64 binary float, little-endian representation.
 
that's uhh a weird feature
 
10:30 AM
Agreed. Same as 0x if followed by more than 8 digits.
 
10:42 AM
yeah two weird features
wonder why they came up with those
 
10:54 AM
In the words of our CTO: This is what happens when APL users get too much influence on language design without pushback from the devt team
 
 
1 hour later…
12:17 PM
@Adám @RubenVerg Do you not need to include uppercase 0x 0b 0r?
 
12:46 PM
ah yeah, missed the "case insensitive" part, will fix later
 
1:34 PM
@RubenVerg Will you add APL64?
 
1:55 PM
@Adám would, if i had the docs!
wait now that I think of it you mentioned a differences list from a+w right
@Adám right, this one
is it accurate? if so might add it without docs
 
That's my understanding. When I get my APL+Win & APL64 license, I can double-check.
 
thanks! might wait for that then, do other dialects in the meantime
 
 
3 hours later…
4:49 PM
@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.
 
5:19 PM
@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.
 
5:35 PM
{d←1⎕DT⍺⍵ ⋄ m←322 379.5 462 ⋄ 3↑⊃¯1⎕DT ⌊/d[1]+m×⌈m÷⍨--/d}
 
 
2 hours later…
7:49 PM
fixed my RIDE now, thx, delete my old RIDE and accidentally delete the interpreter too, this is why I can connect my RIDE 4.5 to dyalog-apl
can. not
Dyalog should bundle the interpreter and RIDE together so that the new users do not go through all the hassle
Dyalog should learn from Steves Job," Just work"
 
 
1 hour later…
9:09 PM
@1234 Heh, speaking of Steve Jobs; on macOS, we currently actually do bundle them and start them together so it "just works".
 
 
2 hours later…
10:52 PM
An article on the (possible) connection between inventors of APL and MATLAB: m.opnxng.com/@steve_7312/…
 

« first day (2584 days earlier)      last day (53 days later) »