it also visually unclear that it's cut, so if you do not know that there is more iutput if you dismiss you cannot guess from the look if ut
This is blocked output ^^^
This is output with dismissed messages
Note, that when it's cut you cannot scroll down to see the rest
The Befunge-93 interpreter pushes an indeterminate number of spaces (32s) to the stack when the instruction pointer wraps around in string mode. This is not in the language specification and does not happen in the Befunge-98 interpreter. Here's a program that shows it, and here's the expected behavior.
(and since 93's grid size is hardcoded, the number of spaces isn't quite indeterminate, so this might actually be intentional)
@m-ender That's a good point. I used "indeterminate" because I just didn't know how many it'd push, I just knew that it did. I did look up the specification again and it really doesn't say what it's supposed to do then, especially since normally the spaces are no-ops; I just decided to report anyways, since it's unexpected (even if compliant), and not in line with some of the other interpreters.
Fairly sure I found a memory leak of some sort
Seem to have found a bug in the evil interpreter. https://tio.run/nexus/evil#@19UmZxSkFj@/38iAA should output 'b' (input + 1) but instead outputs 0 + 1. Seems to be an issue with creating and deleting Wheel cells.
it originally came from here https://web.archive.org/web/20070103000858/www1.pacific.edu/~twrensch/evil/index.html
@moridar719 I copied it here: https://github.com/TryItOnline/evil So I'm guessing you can make a pull request? @DennisMitchell would you be comfortable to accepting a pull request to evil interpreter to fix what appears to be a bug?
@moridar719 I copied it here: https://github.com/TryItOnline/evil So I'm guessing you can make a pull request? @DennisMitchell would you be comfortable to accepting a pull request to evil interpreter to fix what appears to be a bug?
@AndrewSav As long as I can verify that it's actually a bug, gladly.