3 ms·
It unfortunately can't decode :(){ :|:& };:, a classic unintelligible forkbomb. I suppose it's only lack of function support that's the issue! Really neat prog
by scott_karana 13y ago
It unfortunately can't decode :(){ :|:& };:, a classic unintelligible forkbomb. I suppose it's only lack of function support that's the issue!
Really neat program, nonetheless!
- stonewhite 13y agoSee halting problem
- ErsatzVerkehr 13y agoIt's the halting problem, not the parsing problem.
- ToastyMallows 13y agoIt could just compare the literal string and have static explanation just for this command.
- idank 13y agoI'm tempted to add a place holder for all the variations of this forkbomb, until I teach the parser about functions. You'll be amazed how many people try this (or other 'malicious' commands), presumably thinking I'm executing the queries. ;)
- akincisor 13y agoI tried this, but not because I believed that you would execute it, but because a very important use of such a tool would be to explain potentially dangerous commands and their implications.
- redwall_hp 13y agoI searched the classic sudo rm -rf /, too. Just to see if it would adequately explain it.