« first day (38 days earlier)      last day (539 days later) » 

1:26 AM
@WheatWizard: Deadfish~ doesn't care about parentheses at all, so I doubt you'll need to worry about that one
Thutu likes parentheses to be matched within /-delimited sections of a line, although I'm not sure that's mandatory; it also likes lines to end with / unless they start with #
I don't know that much about Japt but IIRC it cares about what goes inside braces; you could try using single quotes inside the braces (i.e. change {…} to {'…'}) to see if that helps
SNUSP has its own entry point so should be very hard to break if you don't break up its code
unbreaking Incident is something of an art form of its own, typically you do that last
and Reng is a 2D language that doesn't parse anything other than the first and last few lines, it tends not to break often; I wonder what you did there?
btw, less than a week left for the next answer
whether zsh or brain-flak classic or something else, I look forward to it :-)
 
1:43 AM
@ais523 I now realize that some of the languages I claimed I had "broken" are just not available on TIO
how long exactly do we have?
 
2:02 AM
until May 1 (next Monday)
 
 
19 hours later…
8:51 PM
Ok it looks like chance has posted his/hers so I will get to work on mine
 
1
A: Add a language to a polyglot

Chance54. Zsh, 1206 bytes #16 "(}23!@)(" 3//*v\D@;'[af2.qc]'#)"14";n4 #/*` PkPPX (22)S"[!(>7 7*,;68*,@;'1,@␉␉␉␉ P''53'S^'q #>␉ # >36!@␉ #`<` #<]+<[.>-]>[ #{ #z} # #=x<R+++++[D>+++++++EAL+++<-][pPLEASE,2<-#2DO,2SUB#1<-#52DO,2SUB#2<-#32DOREADOUT,2PLEASEGIVEUPFACiiipsddsdoh]>+.-- -. >][ #x%+>+=ttt Z_*. #D>

@Chance: Are you running the Incident interpreter locally now? Or did you just copy that bit from my post without realising it had changed?
 
I'm not actually testing it. I've mostly just got a feel for the rules.
 
right, you said you tested it in your post, I'm assuming that's a typo (as you also copied the VIP score from my post in addition to the new one)
 
I think my starting point was answer 54, so I think everything should be included.
 
"Incident was verified to test 33 by running the official interpreter on my own machine."
 
8:54 PM
typically I compare the incident business tokens to the prior answer as part of verification.
 
I tested it on mine, just to be sure; it works
 
cool
 
ok well the zsh really messes up classic
 
dang. really?
I just came over here after posting. so I didn't realize there was another answer cooking
 
yeah [[[]]] prints -1, -1 so I'll have to rewrite zsh/bash
no problem though
 
8:55 PM
hmm, I just realised I had an HTML Incident syntax highlighter lying around
here's the polyglot in all its Incidenty glory: nethack4.org/pastebin/polyglot.html
 
oh wow! cool.
I'm editing that in!
 
that's a temporary link
we can try to find a more permanent home if you like, though
 
oh. yeah
THat's probably best.
 
btw, the highlighter is in the official Incident distribution
I keep running the HTML by mistake (meaning to use a VT100 version to view it in my terminal)
 
I'm in a location where doing anything that's not web based isn't really an option, so HTML is best.
BTW, I didn't check Deadfish~ either. I kinda just stayed away from that space and assumed it would work.
 
9:00 PM
maybe I should finally write that online Incident highlighter I've been working on
also, anything that changes only text after the Deadfish~ code can't affect it, IIRC it isn't even parsing after the first h in the program
I'm not 100% sure it even reads in the input
 
Anyon know if it's possible to get Deadfish~ in Tio?
 
Ask @Dennis
 
I sent him something once, but I don't want to pester him if anyone else has talked with him.
 
we'd need to modify the interpreter to not spam prompts
after doing that, I don't see any reason it wouldn't be addable
I'm slacking on writing that SNUSP interpreter I was planning to write…
 
Ok I made this bash zsh polyglot which contains less [...] but is unbalanced
This works in the two and does minimal damage in Brain-flak and classic
Oh hey its even shorter than the original
 
9:20 PM
I don't think you need the quotes around "1"
 
oh, that's because bash/zsh start an unmatched string in their line
and only end it on a later line
 
hm.
Oh I see
 
wow. well done
 
Ok currently broken are:
Japt
Pyth
Thutu
Alphuck
Unknown are:
Deadfish~
Incident
SNUSP
 
9:34 PM
alphuck is easy. your solution zsh solution has 2 s to in needs 2 preceeding ps
just one additional
 
thanks!
how does that work?
ok I see
Is there any resource for learning how japt works?
 
this is the japt resource ive used
for japt, most of the ployglot lives in a string
it's a backtic initiated string
curlybraces in japt are a way to include code within the string. think string variables.
 
Where is the actual code that does stuff located?
 
I think literal numbers within the curlybraces are the easiest way to deal with japt
 
I assume on the line I'm edditing
 
9:44 PM
no, it's way at the end.
 
currently japt has a problem with the )s in the zsh/bash
 
|1|6$
this is the japt answer
 
japt seemed ok with the )s from my view. this seems like a problem tho: {(<{}(({}){})>)}
 
yeah I just figured that out myself
I wonder what it thinks is going on
 
9:51 PM
lol
 
Oh it shows the decompiled JS
thats helpful
(for people that know JS)
 
yeah, that hasn't been as helpful for me. :P
 
Ok so Thanks to ETHproductions I found the problem
 
Pyth seems like a problem
 
I actually have not fixed Japt yet anyway
there is another place where it is encountering a problem
 
10:06 PM
my old brainflak solution threw a bunch of \ to escape out curly braces.
 
I think that is for Thutu
Ok I'm going to take a break
Thanks for the help
 
both actually
np. :)
 
 
2 hours later…
11:40 PM
Japt is done
Up next is pyth
 
nice
 
What does pyth care about
 
from what I saw, pyth's error was due to the "(("
 
Oh ok
((((((
Thats probably not good then
 
actually just the "(("+...
I believe it's dropping out of a string and parsing 2 un matched open parens
 
11:48 PM
Oh ok yeah I see
hm
 
I think the trick is to find a place to put the (( that's not in quotes and doesn't break prelude
 
Yeah
I think I can move (( to the beginning of the line by the pp
 
cool. that was my thinking too
 
Seems to work
 
Prelude is gonna be tough.
 
11:54 PM
I can't decode the current error though
 
current error?
 
It says its errorring on "Psum" but I am not sure how that is possible
Oh no thats not it
It doesn't like the *
 
pyth works when you run that line in the full polyglot
pyth is another one that parses the whole thing and believes most of it is a string.
 
oh cool
I should have tried that
It looks like adding pyth saved bytes
up next is Prelude
 

« first day (38 days earlier)      last day (539 days later) »