Yeah, evil was landing on the m and then running several things it shouldn't have been. There might be a 1-char fix but I don't have time to find it yet. might be too complex a fix to be worth it though
if that isn't vertically aligned with another (although at this point it seems fairly likely it would be), it'd act as a jump, jumping the Prelude operation to the next matched parenthesis
( means "jump to the column with the matching ) if there are no numbers to the left of this ( on the same row, or if the number to the left on the same row is 0" (approximately, there are some exceptions but they're rarely relevant)
Well looks like i wont be getting literate haskell in till at least tomorrow if it is possible. My computer keeps eating all my mobile data when I connect through mobile hotspot. I did get a rough test done with the current languages, only 3 or 4 broke. But I didn't get the haskell running correctly. I think it was ghc erroring with an exit code of 127, but it could have been the executable generated too. Will have to check tomorrow when I have proper internet.
I've looked at Ook a lot, but that was back when we were still trying to beat the orignal VIP challenge's winning score, and it was always too verbose for that
Ook still could potentially be too verbose per this challenge's rules (I don't even remember what the limits are now, check the question), but I'm not sure. Most trivial bf equivalents were the same way
But back then we were stuck with ~70-80 characters per submission, maybe
And I think the minimal code in BF to print what we needed was about 25 characters, so having to replace each BF command with 3 characters or more meant a lang wouldn't fit
@Chance Yeah, main would be a pain to work with otherwise. m is the landing point for evil's jumps (usually, there's an alternate mode that could get around this) and the a will break things unless shortly followed by a u.
Actually main print is just a nasty combo for evil. p/r also break evil...
m and j are markers, which are landing points for jumps; f initiates a forward jump, and x changes the marking mode (which determines if you land on m or j). There aren't really any lowercase j in the latter half of the program, so you could add an x near the end of the main evil line, then add a j near the end of the program (I'd probably put it with rk's filler s) and that should make the whole second half invisible to evil.
I've avoided using alternate marking mode (with j as landings) thusfar because j is alphuck's output command and, if I recall correctly, alphuck haphazardly executes a whole bunch of random code that by some miracle happens to not cause infinite loops
If we're lucky, that spot near the end won't be executed by alphuck and it'll be an easy switch. Otherwise it'll require more detailed tracing of what alphuck does these days.
Just thinking out loud because I have no idea whether it would be a good idea or not. What do you guys think of adding archway2, assuming we can find the interpreter? Looks to be a 2D brainfuck with loops replaced with conditional reflectors. The IP starts in the lower left.
Wouldn't be our first 2D BF-variant (Minimal-2D). IP starting in the lower left would be interesting. It's worth nothing that the s 8 in the lower left has thusfar been very malleable (before the 8, it's Prelude-padding that's doubled as alphuck/Incident help from time to time), so we have a little leeway there already
@all we could add Ook but it's Ook! Ook! Ook! Ook? Ook. Ook. Ook. Ook. Ook. Ook? Ook. Ook. Ook! Ook? Ook. Ook. Ook? Ook. Ook? Ook! Ook. Ook? Ook? Ook! Ook. Ook? Ook! Ook! Ook! Ook. Ook! Ook! Ook! Ook! Ook! Ook! Ook! Ook! Ook! Ook. (200 characters). How bad is that?
@MDXF The limit's technically 20% of current size, which gives us ~360 about now. So it would technically fit. And since it requires all the punctuation it actually doesn't even affect Moorhens, which I think it now the biggest challenge for adding real-word based BF variants (like There Was Once A Fish Named Fred)
And good luck on that interpreter hunt...similar searches have led me into some weird places on the internet. Finding that dang alphuck interpreter...
Either Cow or alphuck kept taking me to German geocaching sites. One of those did have a working online interpreter, but it was buggy in really weird ways so it seemed like a maintainability nightmare since we didn't have access to the source.
That's why the Cow solution is 20-30 bytes longer than it could have been. Cow can print as an int, but every interpreter except that German one outputs a space after printing as an int.
Well, every interpreter that existed at the time. I've since forked a couple and remedied the problem lol.
That also reminds me I need to finish my trivial bf substitution interpreter, so ANY of the simple variants will always have an interpreter. That also means that I'll have an interpreter that, weirdly, predates some of the languages it interprets.
And since a language is defined by the interpreter...maybe that means you could create bf-variants on the fly for challenges until that loophole is closed? lol.
@MDXF We've been bitten by weird interpreter issues a number of times in this challenge. That's why we're stuck with the one case insensitive alphuck interpreter that seems to exist; however, we've managed to use that to our advantage. On the downside, though, it's cells are way bigger than the usual 8 bytes, so we can't abuse overflow for shorter solutions
That's also why the current driver test for alphuck is considered an abstraction: it works with 8 bit cells and we just make sure we don't actually depend on that at all
I won't have time to for a while, probably. Only managed to slip Commercial in because I'd worked on it for a bit before and because it broke less than I expected it to
Trivial Brainf**k Substitution Interpreter code-golf brainfuck interpreter
Brainf**k is the most famous esoteric programming language and is the inspiration for hundreds of other esoteric languages. In fact, there are quite a few languages that are so heavily based off of Brainf**k that the only...
I don't think that will hose it, but I'm not 100% sure
at least, it looks less obnoxious than some of the things I have to work round, such as <><
(in case you're interested, <>< is the language that made me ask "can I change interpreter?"; I'm trying to work around an arguable bug in the current one)
