Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Thanks. #1

Open
rdebath opened this issue Sep 16, 2017 · 0 comments
Open

Thanks. #1

rdebath opened this issue Sep 16, 2017 · 0 comments

Comments

@rdebath
Copy link

rdebath commented Sep 16, 2017

This infinite loop found a C code generation bug in my interpreter I fixed the bug and (slightly) improved the trivial infinite loop detector,

Small code that crashes the interpreter (10 bytes)
+[+[<>]-]-

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant