A Quine in Fortran 90
medium.com
A Quine in Fortran 90
1–10 of 14 posts
Re: A Quine in Fortran 90
#2I suppose string handling isn't Fortran's strong point!
Re: A Quine in Fortran 90
#3Enjoyed the article. It made me pine for the days when I had time to dedicate a day to just play with code.
Re: A Quine in Fortran 90
#4I may be missing something, but isn't a quine trivial when you use a language that allows for file I/O (which I believe Fortran does have)? Or is the point of the "challenge" to avoid using file I/O?
Re: A Quine in Fortran 90
#5[deleted]
Re: A Quine in Fortran 90
#6I may be missing something, but isn't a quine trivial when you use a language that allows for file I/O (which I believe Fortran does have)? Or is the point of the "challenge" to avoid using file I/O?
I could be wrong, as I only learned about the concept of a quine recently. But the way I understand it, it is good enough to simply output it. I suppose you could write to a file as well, but where would you write to? The wikipedia page for a quine has a lot of examples and all of them seem to simply output to stdout, just as I did. I don't think the challenge talks at any point about I/O, so I do think you can use it if you would want to.
Re: A Quine in Fortran 90
#7I may be missing something, but isn't a quine trivial when you use a language that allows for file I/O (which I believe Fortran does have)? Or is the point of the "challenge" to avoid using file I/O?
I could be wrong, as I only learned about the concept of a quine recently. But the way I understand it, it is good enough to simply output it. I suppose you could write to a file as well, but where would you write to? The wikipedia page for a quine has a lot of examples and all of them seem to simply output to stdout, just as I did. I don't think the challenge talks at any point about I/O, so I do think you can use i…
I didn't mean that you could output to a file -- I meant that, knowing the name of the file the program is saved to (which is possible using facilities available in many modern languages, not sure about Fortran), you can ingest that file and print out its contents (to STDOUT for example).
It feels like cheating, but it's also probably the easiest way to get a true quine which'll always work even if you modify parts of the code (while retaining the part of the program which ingests and prints out the file's contents).
Re: A Quine in Fortran 90
#8Earlier quoted context omitted.
I could be wrong, as I only learned about the concept of a quine recently. But the way I understand it, it is good enough to simply output it. I suppose you could write to a file as well, but where would you write to? The wikipedia page for a quine has a lot of examples and all of them seem to simply output to stdout, just as I did. I don't think the challenge talks at any point about I/O, so I do think you can use i…
I didn't mean that you could output to a file -- I meant that, knowing the name of the file the program is saved to (which is possible using facilities available in many modern languages, not sure about Fortran), you can ingest that file and print out its contents (to STDOUT for example). It feels like cheating, but it's also probably the easiest way to get a true quine which'll always work even if you modify parts o…
#!/usr/bin/env python2.7
print open(__file__, 'r').read()
Re: A Quine in Fortran 90
#9Earlier quoted context omitted.
I could be wrong, as I only learned about the concept of a quine recently. But the way I understand it, it is good enough to simply output it. I suppose you could write to a file as well, but where would you write to? The wikipedia page for a quine has a lot of examples and all of them seem to simply output to stdout, just as I did. I don't think the challenge talks at any point about I/O, so I do think you can use i…
I didn't mean that you could output to a file -- I meant that, knowing the name of the file the program is saved to (which is possible using facilities available in many modern languages, not sure about Fortran), you can ingest that file and print out its contents (to STDOUT for example). It feels like cheating, but it's also probably the easiest way to get a true quine which'll always work even if you modify parts o…
I had the same feeling: https://en.wikipedia.org/wiki/Quine_%28computing%29#.22Cheat...
Re: A Quine in Fortran 90
#10Earlier quoted context omitted.
I could be wrong, as I only learned about the concept of a quine recently. But the way I understand it, it is good enough to simply output it. I suppose you could write to a file as well, but where would you write to? The wikipedia page for a quine has a lot of examples and all of them seem to simply output to stdout, just as I did. I don't think the challenge talks at any point about I/O, so I do think you can use i…
I didn't mean that you could output to a file -- I meant that, knowing the name of the file the program is saved to (which is possible using facilities available in many modern languages, not sure about Fortran), you can ingest that file and print out its contents (to STDOUT for example). It feels like cheating, but it's also probably the easiest way to get a true quine which'll always work even if you modify parts o…
Many years ago, I attempted to cheat this way when writing a JScript quine- but it didn't work because the Windows Scripting Host keeps the source file open while interpreting it, which meant the script couldn't open its own source file because the file was already open in another program!
A proper quine, though, doesn't require input.