The APL Orchard

@ngn Another idea I got was to allow you to "dot" into charvecs (or arrays of charvecs) to access the file content: 'myfile'.Text would be the vector of chars, 'myfile'.Lines would be the vector of lines, .Size etc.

You could even run a function stored in a text file: 'myfile'.Text←'{⍺+⍵}' ⋄ 2('myfile'.Code)3 gives 5

ngn

@Adám not very apl-esque. reminds me of ⍵ in ⎕r's ⍵⍵

Richard Park

1:00 PM

@ngn Are you going to do a Webinar: "The 2019 APL Problem Solving Competition in 33 lines"?

Adám

@RichardPark tbf, only 28 actually have code.

ngn

1:14 PM

@RichardPark i'm afraid of live presentations

but if i win, i could publish a written explanation of the tricky parts

J. Sallé

@ngn booooooooo, I want to see some live-action scans!

Adám

1:33 PM

@ngn I'm afraid you won't; you only use six scans and none are very interesting :-\

1 hour later…

Richard Park

2:43 PM

@ngn Both Dyalog and Vector.org.uk are interested in APL related articles at any time

4 hours later…

J. Sallé

6:16 PM

Looking at this challenge, I wonder if APL could implement ∘ as string composition, as defined by the challenge specs.

Granted, it'd be nearly useless, but I think it'd be neat

Adám

@J.Sallé I don't quite understand the challenge. It sounds close to ,¨ to me.

Adám

6:45 PM

@J.Sallé This little string enhancement tool may interest you.

J. Sallé

6:56 PM

I can't even begin to comprehend it, but the output looks cool

Adám

@J.Sallé It is actually very simple. It is just a single call to ⎕R with a function right operand that selects case based on matched pattern, then takes appropriate action. Should I make a verbose explained version?

J. Sallé

@Adám it would help a lot, yes hahahah

Adám

7:10 PM

Explanation:
https://tio.run/##jVQ9bxNBEO39K0Zp7iycKHFSWUKIFkGIMF0u6NZ3a9@S9a7ZjyQWhAIkC0VyBEKRaGigoUCiSkPJT7k/Ymb2nMs5uGCL097OzJt5M2@XTeRmPmVSjxaLfjn7@LoFUM5/466c/8TdV2AnWuRwwqTnwI3RBsQQMiYlz@FUuEJ7t7QyY9i0hQAT5hw3yi5RVhdhCiWcYFJYXvs2wjoUd/EuSpP8Xho1wg63j2DAsmMnsmPMLlTOzyAWymlwBa@rGPkxV669DvHwRXp0gxkQd1YQ@dnEcGuFVhCP2RSUdpBp5ZhQtZtdB5wkdaFL4G4FbCWzRR27NtJv4XqTJFtRFbnbjJSc3IGpnNq@4TeIqYKh9gYKZJ@LkXCWmt73A@toggHF0p9w3hGXoVdZ2GzeDA73nGUFjJnLihYV3b1fzq@3Dqrq9v24FzUY3Zne8IYFKD8eYHnItgdecZuxCW@yBdi9i1teXj3qP92PNqIOWZ5QBR38@wcbG9GDCarrldeOWxys9tiG0AqFHjgqB8wCoUGVugX/uygXl6g/0lRcKSkICcXfBhQ5KSN@eP…

J. Sallé

@Adám now that's pretty didatic!

I loved it

Adám

7:41 PM

@J.Sallé Thanks. Should I add it as $ in Extended?

J. Sallé

@Adám most definitely

Adám

@J.Sallé There's one slight complication. It uses ⍎ which would execute in the place where the cover function is defined. I need to make it execute where the caller is. I think that's pretty easy to solve though.

J. Sallé

@Adám I'd love to see the final version

Adám

@J.Sallé I think it is as simple as replacing ⍎ with (⊃⎕RSI)⍎. This also allows me to use variables inside the definition. The original didn't because I feared they might shadow values the user wanted in backticks.

J. Sallé

I don't know what that quad does though

Adám

7:53 PM

@J.Sallé It is a vector of references to spaces where each level of the stack was called from, so the first element is "my caller's space". That's where we want to execute. RSI is Reference-to-Space Indicator

Compare with ⎕NSI which is Name-of-Space Indicator

They correspond to ⎕SI which is the State (or Stack) indicator, i.e. the names of my callers up the stack.

J. Sallé

Ah, I see

There's a lot of stuff I still need to learn about APL, I see hahahahah

« first day (916 days earlier) ← previous day next day → last day (1755 days later) »

all rooms