1494
Comment:
|
1870
add the solution that i came up with when someone asked about quines 4 days ago
|
Deletions are marked like this. | Additions are marked like this. |
Line 37: | Line 37: |
This other one consists of a function that uses `declare -f` to print its own definition and the remaining code. The function's code needs to be written in this precise format and there needs to be a trailing space after `f ()` and `{` to match `declare -f`'s output. {{{#!highlight bash #!/bin/bash - f () { echo '#!/bin/bash -'; declare -f f; echo f } f }}} |
|
Line 40: | Line 54: |
CategoryShell CategorySillyThings | CategorySillyThings |
Bash quine
A quine is a program that takes no input, and prints its own source code as output. Writing one is challenging in any language, and usually involves poking into the darkest, smelliest corners of the syntax.
If you've come across this page through some sort of wandering browsing, you might wish to stop reading after this introduction, and attempt to write a quine yourself. Reading the finished results here is not as educational as the struggle to write one. If on the other hand you've already struggled, either successfully or unsuccessfully, and would like to compare your results against someone else's, then read on.
Invalid quines
The classic shell approach would be something like
However, this is considered invalid, as it takes input from the file system.
The other classic shell approach would be the empty program. This one is considered to fail the spirit of the challenge, because it doesn't teach you much.
Valid quines
This first one is derived from the Java quine posted on the wikipedia page.
This other one consists of a function that uses declare -f to print its own definition and the remaining code.
The function's code needs to be written in this precise format and there needs to be a trailing space after f () and { to match declare -f's output.
(May add more later if I figure them out.)