Wikipedia says it's called a quine and someone gave the code below:
char*s="char*s=%c%s%c;main(){printf(s,34,s,34);}";main(){printf(s,34,s,34);}
But, obviously you have to add
#include <stdio.h> //corrected from #include <stdlib.h>
so that the printf()
could work.
Literally, since the above program did not print #include <stdio.h>
, it is not a solution (?)
I am confused about the literal requirement of "print its own source code", and any purpose of this kind of problems, especially at interviews.
Here's a version that will be accepted by C++ compilers:
test run:
The string
s
contains mostly a copy of the source, except for the content ofs
itself - instead it has%c%s%c
there.The trick is that in the
printf
call, the strings
is used both as format and as the replacement for the%s
. This causesprintf
to put it also into the definition ofs
(on the output text, that is)the additional
10
and34
s correspond to the linefeed and"
string delimiter. They are inserted byprintf
as replacements of the%c
s, because they would require an additional\
in the format-string, which would cause the format- and replacement-string to differ, so the trick wouldn't work anymore.The main purpose of interview questions about quine programs is usually to see whether you've come across them before. They are almost never useful in any other sense.
The code above can be upgraded modestly to make a C99-compliant program (according to GCC), as follows:
Compilation
Code
Note that this assumes a code set where
"
is code point 34 and newline is code point 10. This version prints out a newline at the end, unlike the original. It also contains the#include <stdio.h>
that is needed, and the lines are almost short enough to work on SO without a horizontal scroll bar. With a little more effort, it could undoubtedly be made short enough.Test
The acid test for the quine program is:
If there's a difference between the source code and the output, it will be reported.
An almost useful application of "quine-like" techniques
Way back in the days of my youth, I produced a bilingual "self-reproducing" program. It was a combination of shell script and Informix-4GL (I4GL) source code. One property that made this possible was that I4GL treats
{ ... }
as a comment, but the shell treats that as a unit of I/O redirection. I4GL also has#...EOL
comments, as does the shell. The shell script at the top of the file included data and operations to regenerate the complex sequence of validation operations in a language that does not support pointers. The data controlled which I4GL functions we generated and how each one was generated. The I4GL code was then compiled to validate the data imported from an external data source on a weekly basis.If you ran the file (call it
file0.4gl
) as a shell script and captured the output (call thatfile1.4gl
), and then ranfile1.4gl
as a shell script and captured the output infile2.4gl
, the two filesfile1.4gl
andfile2.4gl
would be identical. However,file0.4gl
could be missing all the generated I4GL code and as long as the shell script 'comment' at the top of the file was not damaged, it would regenerate a self-replicating file.The trick here is that most compilers will compile without requiring you to include
stdio.h
.They will usually just throw a warning.
Quine (Basic self-relicating code in c++`// Self replicating basic code
[http://www.nyx.net/~gthompso/quine.htm#links] [https://pastebin.com/2UkGbRPF#links]
// Self replicating basic code