You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This infinite loop found a C code generation bug in my interpreter I fixed the bug and (slightly) improved the trivial infinite loop detector,
Smallcode that crashes the interpreter (10bytes)+[+[<>]-]-
But as for the rest, I'm not really sure you're detecting what you think you are.
kill.bf
vim syntax highlight says this is just a comment. So your Woah message shouldn't be run.
killfuck_s2.bf
Error: "Tape pointer has moved below available space"
kill_s.bf
This is just an infinite loop; BUT it triggered a code generation error in Tritium.
kill_small.bf
Optimised to nothing.
Your big script is more interesting killfuck.bf gives the message Warning: unbalanced bracket at Line 3, Col 1827 It then prints it's initial message (Note: requires 8-bit interpreter.) After that there's an infinite loop that's not entered because it's initial value is zero and a the loop comment containing your Woah message.
The text was updated successfully, but these errors were encountered:
This infinite loop found a C code generation bug in my interpreter I fixed the bug and (slightly) improved the trivial infinite loop detector,
But as for the rest, I'm not really sure you're detecting what you think you are.
vim syntax highlight says this is just a comment. So your
Woah
message shouldn't be run.Error: "Tape pointer has moved below available space"
This is just an infinite loop; BUT it triggered a code generation error in Tritium.
Optimised to nothing.
Your big script is more interesting
killfuck.bf
gives the messageWarning: unbalanced bracket at Line 3, Col 1827
It then prints it's initial message (Note: requires 8-bit interpreter.) After that there's an infinite loop that's not entered because it's initial value is zero and a the loop comment containing yourWoah
message.The text was updated successfully, but these errors were encountered: