talk.tryitonline.net

« first day (370 days earlier) ← previous day next day → last day (2124 days later) »

Luis Mendo

12:11 AM

@Dennis Can you please pull MATL when you have some time?

Dennis

@LuisMendo Done.

@Pavel Just like on Windows. tio.run/##Jcw9CsJAEEDhOnuKMVUC/…

Pavel

12:53 AM

Cool

Now I can fail at pointers and use unnecessary syntactic sugar at the same time.

@Dennis I think you missed this feature-request earlier, but it would be great if while searching columns were wider, after you type "half" and there's only one result to display, there's not really a reason to cut it off with a ....

Dennis

@Pavel The space is split with column-width. Specialcasing only a few results will take something else.

Pavel

Could you just increase column-width if the amount of results is low, and then increase it again as the search field gets cleared?

2 hours later…

Dennis

3:23 AM

@cairdcoinheringaahing Doesn't work.

Traceback (most recent call last):
  File "/opt/deorst/interpreter.py", line 693, in <module>
    run(prog, argv)
  File "/opt/deorst/interpreter.py", line 678, in run
    inputs = list(filter(lambda a: a not in flags))
TypeError: filter expected 2 arguments, got 1

6 hours later…

Luis Mendo

8:55 AM

@Dennis Thank you!

1 hour later…

caird coinheringaahing

9:59 AM

@Dennis could you try it now?

4 hours later…

Luke

2:19 PM

@Dennis: please update Japt

1 hour later…

Adám

3:42 PM

"Tio" means 10 in Swedish, 'cause TIO is 10/10.

Dennis

caird coinheringaahing

@Dennis does Deorst work now? I think I've fixed all the bugs

Dennis

@cairdcoinheringaahing Yes, that works. I have to ask though: what's up with stdin.txt and stdout.txt? Why not use the actual streams?

caird coinheringaahing

@Dennis I didn't like the way that the Python file took input (via the shell) and couldn't find a better way. Just don't ask :D

Dennis

Too late, I already did. :P

caird coinheringaahing

3:46 PM

I don't have a good explanation :( I just did

Dennis

It doesn't matter for TIO, but there's no clear consensus on PPCG yet that taking input from a file is acceptable.

@cairdcoinheringaahing tio.run/##S0nNLyou@f9f3SM1JydfRyE8vygnRVHd//9/AA

caird coinheringaahing

@Dennis Thanks!

caird coinheringaahing

4:19 PM

@Dennis can you pull Deorst please?

Dennis

4:56 PM

@cairdcoinheringaahing Syncing.

caird coinheringaahing

5:22 PM

@Dennis I hate to ask again, but could you pull Deorst when you get a chance? Thanks in advance

Dennis

5:57 PM

@cairdcoinheringaahing Syncing.

caird coinheringaahing

@Dennis thanks

caird coinheringaahing

7:02 PM

@Dennis can you pull it again? Note to self: think of different ways to ask for a language pull

Dennis

7:50 PM

@cairdcoinheringaahing Syncing.

Pavel

8:29 PM

@Dennis Idea: ln -sf /dev/stdout stdout.txt

Dennis

9:20 PM

That one way to do it, I guess.

Zacharý

Fair warning, I'll need MY pulled soon, not yet, but soon. I thought I had functional-commands working with command-line arguments.

@Dennis, like now. Can you pull MY? I think I fixed the bug now.

Pavel

@Dennis TIO has interactive i/o as one of its long-term plans, right?

Symlinking stdout.txt to /dev/stdout allows for that, otherwise it will be forced to all be output at the end.

Dennis

9:43 PM

@Zacharý Syncing.

@Pavel Emphasis on long, yes. Symlinking will mitigate buffering, but nothing else.

caird coinheringaahing

10:37 PM

@Dennis can you pull Deorst please?

Dennis

10:57 PM

@cairdcoinheringaahing Syncing.

caird coinheringaahing

11:08 PM

@Dennis Thanks

Downgoat

11:49 PM

@Dennis for LLVM IR right now it is just lli (interpret). Can you make that into a llc (compile) + ./prog that way we can do compiler args + args to program?

caird coinheringaahing

@Dennis can you pull it again? Sorry, I'm working on new features that I forgot to add in the first place .

Dennis

@Downgoat Sure, but that's how lli works as well. Compiler flags are placed before the filename (making them options), user args are placed after it. llvm.org/docs/CommandGuide/lli.html

Downgoat

huh ok. I completely missed the "Compiler flags" tab at the very top >_<