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

brainfuck example is not a fork bomb #18

Open
Mee42 opened this issue Aug 8, 2020 · 4 comments
Open

brainfuck example is not a fork bomb #18

Mee42 opened this issue Aug 8, 2020 · 4 comments

Comments

@Mee42
Copy link

Mee42 commented Aug 8, 2020

it is an infinite loop. If you were to convert it to C, it would look like this:

void run(int* mem) {
    *mem++;
    while(*mem) { mem++; *mem++; };
}

which is very clearly not a fork bomb

@Mee42
Copy link
Author

Mee42 commented Oct 11, 2020

Please don't yell

No one answered because the maintainer isn't maintaining this project, and no one other then the maintainer would give af

@ghost
Copy link

ghost commented Feb 10, 2021

This is correct, it is not a correct brainfuck fork bomb, I have come across a solution (not) by myself, it is not a fork bomb but it leaves traces.

+[[+]>+]

@ghost
Copy link

ghost commented Feb 10, 2021

This might cause a system to crash if left long. `+[[.+]+]

@Xprogrammer777
Copy link

This is correct, it is not a correct brainfuck fork bomb, I have come across a solution (not) by myself, it is not a fork bomb but it leaves traces.

+[[+]>+]

btw brainfuck is only brainfuck

KoraggKnightWolf added a commit to KoraggKnightWolf/fork-bomb that referenced this issue Dec 12, 2022
Taken from aaronryank#18 with the intention to provide a hopefully more correct version
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

2 participants