@Dennis I suspect this has been asked but still

why Assembly (whatever) but Whatever Scheme?

@DestructibleLemon i guess

@Dennis made a pull request which I merged

@DestructibleLemon yep, I can see that now. Perhaps he forgot to check-in the wrapper update

Thank you for clearing that up

@Dennis last working commit of sad-flak with the wrapper that is in the TIO repo is b47a1ca4dd92863b3d93774ddf8a413d6d3b0dd4

This is right before your pull request was merged

Can you have a look when you are around please?

Ah okay, I finally caught up, you did not even pull the the merged pull request (tio.run/##S0oszvj/Pz2zREHXWUE/…) and when you do you will naturally update the wrapper. Sorry for the noise

me?

I'm confused

@DestructibleLemon no, Dennis

ok

@DestructibleLemon I just rebuild TIO mirror and I got a error. The error was because the build script pulls the latest from github so I got the latest commit of sad-flak, but in order for it to work TIO wrapper needs updated, which Dennis could not do because he did not get to look/pull the merged sad-flak code yet. So all good.

Hope that makes sense ;)

@Dennis how are "command line parameters" specified on TIO?

@Dennis could you pull Husk please?

@Leo Done.

@Adám In the Arguments section.

@AndrewSavinykh @DestructibleLemon TIO is running the latest version of Sad-Flak now.

@Dennis So every language is custom wrapped get its command line arguments from the correct argument?

As long as I didn't mess anything up, yes. Some languages treat parameters before and after the code (usually a file name) differently, so these have Options enabled as well. Compiled languages usually jave Compiler flags. Java has both.

@Dennis Options? Ah, I see by Java. Neat.

@Dennis So I'm making two new languages. I will need input (the data to be processed); that goes in Input. There's code; Code. And some options that would conveniently fit in Options. If I take filenames for each of those, is that good for you?

@Dennis Actually, what are the correct uses of Input vs Arguments?

Input comes from STDIN.

The "normal" invocation is:

<interpreter> "${TIO_OPTIONS[@]}" .code.tio "$@" < .input.tio

.code.tio is specified as a parameter between options and arguments, .input.tio is piped/redirected.

@Dennis I'm thinking that the language can be called separately for each argument, so if there are multiple test cases, they can all be run at once. Could the wrapper contain a loop for that?

@Dennis Thank you. I hope it's not a problem if we'll keep asking for pulls in the next days... we're still developing many missing features

@Adám No, all wrappers do one invocation. If you want to process arguments like this, you'd have to do that in your language. I do hope to implement multi-part requests soon, which would make this kind of thing obsolete.

@Dennis Hm, how can I get multiple multi-line arguments/inputs?

@Leo Not an issue. Updates are easy; I have scripts that take care of them automatically. There can be a rather long delay when I'm not home though.

Perfect, thank you :)

@Adám Not sure I understand. Input and Arguments are text areas and will happily take multi-line text.

@Dennis How do you put multi-line text on a commandline?

Depends on your shell. Bash happily takes multi-line arguments if you quote them.

@Dennis Not sure how to get them into APL though. If I had a list of file names I could loop through them.

@Dennis Can you add the two languages ⎕R and ⎕S? github.com/abrudz/QuadRS

@Adám I think that .arguments.tio in your wrapper should be "$@"

IDK how it works tho

@Phoenix Would it then just insert the value of the first argument there?

IDK what you're trying to achieve, just know that .arguments.tio is not a file that exists.

tio.run/##S0oszvj/P6dYQdfx////afn5/5MSiwA

@Phoenix How about now?

That looks like something that works, but I thought you mentioned wanting to be able to take multiple arguments?

Currently all but the first would be ignored

@Phoenix Yes, the arguments are just option flags.

@Phoenix What I wanted is the ability to run multiple test cases in one go.

So if I call it with -a -b it would only see -a

@Phoenix you should call it with ab

@Phoenix maybe I should change that so it can take -a -b and just remove all spaces and dashes?

Nah. If the language only has one argument to take, then the current setup is fine.

@Phoenix It is really multiple options, a would one option, b would be an unrelated option. I'll allow both.

Here's an issue: '$1' doesn't work because single quoted strings don't support interpolation

@Phoenix But I use double-quoted.

'R'Run '$1'

'$1'

@Phoenix "'.code.tio'('R'Run '$@')'.input.tio'"

Oh wait, I see what you're doing.

Too many quotes >_>

Is ⎕ a square or something my browser can't render?

In the language name

@Phoenix It is an APL Quad hex 2395

Ah

What are these langs anyway? What does Hello, World! look like?

@Phoenix Code would be \nHello World!

Are ⎕R and ⎕S already something builtin to APL that you made a wrapper for?

Your code seems rather short to interpret a language.

@Phoenix Yes, exactly. But The wrapper makes them significantly golfier.

Ah

@Adám I'll take a look.

@Dennis Can you please pull Brachylog?

@Fatalize Done.

Vielen Dank

Gern geschehen.

...my German ain't that good

despite studying it for like 9 years

forgot everything

there is always google translate ;)

also everybody knows danke/bitte in a few languages ;)

@Fatalize I managed to ask for directions in Munich (in German) despite only studying German for few hours. Conclusion: German is easy.

Well you speak Danish, you have a slight edge

though it's small

@Fatalize I speak Yiddish. I have a major edge.

Cheater!

@Adám asking is half the deal, understanding the answer might be the difficult part. Although, with all the gesturing, which are international, probably manageable even in Icelandic

@AndrewSavinykh Í alvöru?

and google translate ;)

@AndrewSavinykh There was an Italian who got killed while walking along the tracks of the local trains in Stockholm, Sweden. The guards called him over by scooping their hands up, which in Italian means Go! He started running, so they shot him.

@Dennis Thank you. As mentioned to Phoenix, HW in both languages is just that Input should be a newline followed by the desired text.

Alright, thanks. The font on the language selection page isn't going to like the quad. :P

@Dennis What's the worst that could happen? It would display as tofu? That's perfect.

If it can't find the symbol, it will draw it as the symbol not found thing, which is... still a rectangle.

Not that easy. It first goes through other available fonts.

@Dennis So? It disturbs you that it'll mess up the looks of your site?

I have to confess, I'm not particularly happy about this. :P

@Dennis You could call them QuadR and QuadS or just Replace and Search, which are the official names.

Those names would be used in the auto-generated SE answers as well then. I figured you'd like to see ⎕R and ⎕S in those.

@Dennis Yeah.

@Dennis How about using a different character that the font does have?

How about using a character that's not in any of the fonts

@feersum What? That's the whole problem.

Heh, I guess that would work too. :P

Oh, I see. :-)

Unfortunately, none of ☐◻▯ are in Exo 2.

COuld use ם but that's a RTL char…

ߛR and ߛS ?

@feersum Actually, ૹ renders ok in Exo 2 (as undefined)

□ is in the font.

@Dennis How about "APL Replace" and "APL Search"?

It's your language. ¯\_(ツ)_/¯

DOMAIN ERROR: Invalid regular expression format
Run[27] output←from ⎕R to⍠options⊢input

Did I misunderstand the HW test?

@Dennis tio.run/…

@Dennis Calling them APL Replace and APL Search will sort them right after the other APLs, which might be a good thing.

Oh, was I supposed to classify them as practical?

@Dennis Oh, no, actually, maybe not. Didn't think of that.

@Dennis How about "Replace (Dyalog APL)" and "Search (Dyalog APL)", because if we don't mention the actual ⎕ names, it isn't right to call it general "APL"?

It's your language. The name is up to you.

@Adám Did you try with a file?

@Dennis Uh, no. Oups.

@Dennis Sorry about that. Found the bug.

Is replace essentially Retina?

@Adám OK, let me know when you fix it. I'll be afk for a few hours.

@Phoenix Yes, but using PCRE enhanced by APL. It allows calling any APL code on each match, and allows access to stored information from previous matches.

Isn't Dyalog regex .NET regex

@Phoenix Has both, but no need to cover the .NET regex; there's Retina for that.

@Dennis OK, should be fixed now.

@Dennis I've updated README.md with languages.json entries. Anything else I can do to assist?

Thanks, but those were already done. I didn't go live because the HW test was failing.

@Adám You specified SBCS. Would the languages work with Dyalog Classic as well?

@Dennis yes, unmodified, as long as one doesn't input characters that are not in the character set. Just like Classic and Unicode take the same sources.

Right. The language IDs and names are a tad inconsistent. Why not simply call it Quad R? That's a tad catchier than Replace (Dyalog APL).