64
\$\begingroup\$

Long-time lurker, first-time poster. So here goes.

In the Wikipedia page for quine, it says that "a quine is considered to be 'cheating' if it looks at its own source code." Your task is to make one of these "cheating quines" that reads its own source code.

This is , so the shortest code in bytes - in each language - wins. This means that a 5-byte Pyth script would not beat a 21-byte Python script - but a 15-byte Python script would.

You must use file I/O to read the source code, so the following JavaScript code, taken from the official Wikipedia page, is invalid:

function a() {
    document.write(a, "a()");
}
a()

It must access the source code of the file on disk.

You are not allowed to specify the file name. You must make it detect the filename itself.

Everyone clear? Go!

\$\endgroup\$
15
  • 1
    \$\begingroup\$ Is a trailing newlines not present in the original file allowed? \$\endgroup\$
    – isaacg
    Commented Oct 29, 2015 at 22:04
  • 3
    \$\begingroup\$ @isaacg IMHO That's not a quine, since it is not the source code. \$\endgroup\$
    – user42643
    Commented Oct 29, 2015 at 22:05
  • 3
    \$\begingroup\$ You should state a requirement that it determine the actual filename instead of assuming a hard-coded string for the source location. \$\endgroup\$
    – feersum
    Commented Oct 29, 2015 at 22:26
  • 3
    \$\begingroup\$ I agree with @feersum though, that requiring a specific file name makes this challenge way to trivial. \$\endgroup\$
    – user42643
    Commented Oct 29, 2015 at 22:33
  • 2
    \$\begingroup\$ Can we assume that (for compiled languages) the source code is in the same folder (i.e. we can just add ".cpp" or ".hs" to arg[0] to get the source). \$\endgroup\$
    – HEGX64
    Commented Nov 1, 2015 at 9:15

83 Answers 83

66
\$\begingroup\$

Zsh, 4 bytes

<$0

The Z shell has feline functionalities built in. The fourth character is a linefeed.

Try it online!

The code does not depend in any way on the file name; it works even if the file name contains special character, such as spaces or newlines.

Test run

$ cat "my quine.sh"
<$0
$ zsh "my quine.sh" 
<$0
$ diff -s <(zsh "my quine.sh") <(cat "my quine.sh")
Files /dev/fd/63 and /dev/fd/62 are identical
\$\endgroup\$
1
  • 44
    \$\begingroup\$ feline functionalities :) \$\endgroup\$
    – theB
    Commented Oct 31, 2015 at 10:51
49
\$\begingroup\$

Bash, 6 bytes

cat $0

Basically.

\$\endgroup\$
28
  • 3
    \$\begingroup\$ It does not print a newline. \$\endgroup\$ Commented Oct 29, 2015 at 22:06
  • 3
    \$\begingroup\$ cat does not append a newline (at least on my system). \$\endgroup\$ Commented Oct 29, 2015 at 22:06
  • 8
    \$\begingroup\$ @isaacg cat prints the content of the supplied file byte per byte. \$\endgroup\$
    – Dennis
    Commented Oct 29, 2015 at 22:17
  • 2
    \$\begingroup\$ @LukStorms But wouldn't this be a cat solution then, instead of a bash solution? And cat does not really qualify as programming language \$\endgroup\$ Commented Oct 29, 2015 at 23:07
  • 37
    \$\begingroup\$ Will this work if the file is named -e ? \$\endgroup\$ Commented Oct 30, 2015 at 6:05
38
\$\begingroup\$

UNIX executable loader, 10 bytes

#!/bin/cat

If you don't care about spam on standard error, you can make it one byte shorter:

#!/bin/dd
\$\endgroup\$
7
  • 9
    \$\begingroup\$ I like this. Not sure if it qualifies as a "language," though. \$\endgroup\$
    – Kevin
    Commented Oct 29, 2015 at 23:39
  • 3
    \$\begingroup\$ I'm not suggesting you do btw. I'm suggesting you could \$\endgroup\$ Commented Oct 30, 2015 at 9:54
  • 3
    \$\begingroup\$ @Kevin The "language" (that is, interpreter) is cat. And I guess if you want to be very specific, a cat program simply prints itself, and is compatible with every file format in existence :) \$\endgroup\$
    – l0b0
    Commented Oct 30, 2015 at 10:38
  • 2
    \$\begingroup\$ @JamesWebster sudo install /bin/cat /c. Y'know, just in case /bin isn't on the root filesystem. Gotta have that cat in singleuser… \$\endgroup\$ Commented Oct 30, 2015 at 23:08
  • 1
    \$\begingroup\$ @l0b0: The "language" here is not cat. The interpreter we play with here is within the kernel (e.g., Linux), which reads the first two bytes (magic bytes) of a file given to it in order to execute it, and if it finds them to be #!, it continues to read the line to get a path of another executable which it will then execute, passing the file's path as an argument to it. The interpreter here is not cat, but part of the kernel. cat is just invoked after the kernel interpreted the first line, and then just does the file I/O. Here it is the same as with the bash-answer (cat $0) above. \$\endgroup\$ Commented May 12, 2017 at 20:14
25
\$\begingroup\$

C, 52

s[99];main(){read(open(__FILE__,0),s,99);printf(s);}

Of course, this reads the source code and not the compiled program - I assume that's within spec.

\$\endgroup\$
11
  • \$\begingroup\$ You could use printf instead of puts to avoid a trailing newline. \$\endgroup\$
    – feersum
    Commented Oct 29, 2015 at 22:51
  • 20
    \$\begingroup\$ @DigitalTrauma It's because of your avatar, of course \$\endgroup\$ Commented Oct 30, 2015 at 6:27
  • 4
    \$\begingroup\$ Actually, puts can be used, you just need to read fewer characters. \$\endgroup\$ Commented Oct 31, 2015 at 1:41
  • 2
    \$\begingroup\$ @kasperd Yes, guaranteed by C89 \$\endgroup\$ Commented Nov 1, 2015 at 0:06
  • 1
    \$\begingroup\$ Save two bytes: s[50];main(){read(open(__FILE__,0),s,50);puts(s);} by reading only 50 characters you skip the possible newline and can use puts instead of printf. \$\endgroup\$
    – MD XF
    Commented May 24, 2017 at 3:04
23
+200
\$\begingroup\$

Vyxal 2.4.0, 50 bytes

`\");VY_print(chr(96)+code.split('\n')[3][15:-4])#

Vyxal doesn't have a way to read files, but in v2.4.0 and prior, there was an ACE exploit that allowed for arbitrary python to be executed.


The ACE:

Vyxal is a transpiled language, meaning that every command in a program is converted to some python code, and then all of the python code is combined together and executed.

When pushing a string, all that was done to the string in transpilation was changing " to \\\", then appending it to the stack. This meant that a string \"); # would become \\");#. On its own, this means nothing, but when considered in the transpiled code, it is much more useful.

When viewing the transpiled code (which you can do for any Vyxal program using the c flag), you can see that the snippet `\\"); # is transpiled to the following python code:

stack.append("\\"); #\n")

Instead of pushing the string that we told it to, it simply pushed \, followed by a comment. In theory, we could put any python code between the ; and the #, which is what we do in this program.


The program:

In this program, the payload (the python code that we actually care about) is the following:

VY_print(chr(96)+code.split('\n')[3][15:-4])

This has several parts to it, so lets pick it apart bit by bit.

VY_print is the printing function that is defined internally in Vyxal. I used this function instead of print because it disables the implicit output that Vyxal normally has. This prints the final string, which will hopefully be the same as the program.

When the program is transpiled, the transpiled code is saved in the code variable. This variable is used in the program to read the source code, which makes this a cheating quine.

However, the code variable also contains a header that initializes a few variables, such as the stack. To combat this, we split the code on newlines and get only the fourth line, which is where our code is.

Unfortunately, this line also has the stack.append..., and the comment at the end, neither of which are part of our quine. Because of this, we need to take only the 16th through 5th-to-last characters in the string, which we do with [15:-4].

Finally, our code has a backtick at the beginning to start the string, so we add one to the beginning of the output with chr(96), since the ASCII value of ` is 96.

\$\endgroup\$
1
  • 8
    \$\begingroup\$ Wooooo crappy programming ftw! \$\endgroup\$
    – lyxal
    Commented Jul 8, 2021 at 11:55
14
\$\begingroup\$

Perl, 15 bytes

open 0;print<0>

Saved 3 bytes thanks to @ThisSuitIsBlackNot!

\$\endgroup\$
3
  • 2
    \$\begingroup\$ You can save 3 bytes with open 0;print<0> \$\endgroup\$ Commented Nov 2, 2015 at 3:45
  • \$\begingroup\$ @ThisSuitIsBlackNot I was sure there was a shorter way to do it, but I couldn't for the life of my work it out... Using 0 assumes $0 then? \$\endgroup\$ Commented Nov 2, 2015 at 5:44
  • 3
    \$\begingroup\$ Yep. See perldoc -f open: "As a shortcut a one-argument call takes the filename from the global scalar variable of the same name as the filehandle: $ARTICLE = 100; open(ARTICLE) or die "Can't find article $ARTICLE: $!\n";" \$\endgroup\$ Commented Nov 2, 2015 at 6:41
13
\$\begingroup\$

PHP, 21 Bytes

<?=file(__FILE__)[0];

file reads a file line by line into an array and the file only has one line. This saves a byte in comparison to readfile(__FILE__).

\$\endgroup\$
3
  • \$\begingroup\$ Notice that this only works from PHP5.4 and up, which was the first version to support array de-referentiation. But other than that, quite a nice answer! \$\endgroup\$ Commented Nov 3, 2015 at 9:19
  • 1
    \$\begingroup\$ readfile is also 21: <?readfile(__FILE__);. \$\endgroup\$
    – primo
    Commented Nov 3, 2015 at 15:42
  • 1
    \$\begingroup\$ Right, it doesn't need <?= \$\endgroup\$ Commented Nov 3, 2015 at 15:55
13
\$\begingroup\$

Perl 6, 20 bytes

print slurp $?FILE

I haven't worked with Perl 6 very long so I'm not sure if there are any tricks to make this shorter.

\$\endgroup\$
2
  • 2
    \$\begingroup\$ can you remove the second space? \$\endgroup\$
    – Eevee
    Commented Nov 1, 2015 at 2:03
  • 5
    \$\begingroup\$ @Eevee nope, it gets angry \$\endgroup\$
    – Hotkeys
    Commented Nov 1, 2015 at 9:25
12
\$\begingroup\$

osascript (AppleScript from the command line), 40 33 32 bytes

(read path to me)'s paragraph 1

Executing on a file called a with osascript a.

Gets the first paragraph (line) of the file and prints it to STDOUT with a trailing newline, therefore the newline in the code.

\$\endgroup\$
4
  • 1
    \$\begingroup\$ See my edit to the OP \$\endgroup\$ Commented Oct 29, 2015 at 23:03
  • \$\begingroup\$ Working on getting it to work. \$\endgroup\$ Commented Oct 29, 2015 at 23:07
  • \$\begingroup\$ read path to me seems to work for me. El Cap. \$\endgroup\$ Commented Oct 29, 2015 at 23:15
  • \$\begingroup\$ Didn't see this, but this is the way I ended up doing it. :P Thanks, @DigitalTrauma. EDIT: trailing newlines must be considered, so you add the newline and use paragraphs 1. \$\endgroup\$ Commented Oct 30, 2015 at 7:30
12
\$\begingroup\$

Python 2, 32 bytes

There's a newline at the end of the file.

print open(__file__).readline()

Python 3, 33 bytes

There's a newline at the end of the file.

print(open(__file__).readline())

Thanks to feersum for catching a problem and supplying __file__, Loovjo for a new approach to the Python 2 solution that saved 17 bytes, and Skyler for a solution that saved yet another byte and worked in both Python 2 and 3 (pending print being a function in Python 3)!

Doc link for readline

\$\endgroup\$
8
  • \$\begingroup\$ This would also save 2 bytes in python3 because you could discard the end parameter. \$\endgroup\$
    – Skyler
    Commented Nov 2, 2015 at 21:24
  • \$\begingroup\$ @Skyler You're absolutely correct. \$\endgroup\$
    – Celeo
    Commented Nov 2, 2015 at 21:34
  • \$\begingroup\$ How does this work in Python 3, which needs parens for print? \$\endgroup\$
    – Doorknob
    Commented Nov 2, 2015 at 21:36
  • \$\begingroup\$ Python 3 should be print(open(__file__).readline()) followed by a newline. \$\endgroup\$
    – Skyler
    Commented Nov 2, 2015 at 21:37
  • \$\begingroup\$ Your Python 3 example says Python 2 rather than Python 3 \$\endgroup\$ Commented May 25, 2016 at 22:39
12
\$\begingroup\$

Python 2.7, 30 bytes

print open(__file__).read(29)

Edit: Just to be clear, the code above is supposed to have a newline at the end as the 30th byte. I'm not familiar with markdown enough to figure out how to display it in the code block.

I'm using the same trick here as the one in my C submission. This reads the whole source file excluding the trailing newline to account for the additional newline which print will append to the output.

\$\endgroup\$
4
  • \$\begingroup\$ Does this run into the same problem with the trailing newline that the other submission did? \$\endgroup\$
    – cole
    Commented Oct 30, 2015 at 0:21
  • \$\begingroup\$ No. There's supposed to be a trailing newline that makes the 30th byte in the source code but I can't get it to display in the code block. My submission works because it reads the first 29 bytes of the source code so that the newline from print won't be extraneous. \$\endgroup\$
    – xsot
    Commented Oct 30, 2015 at 0:25
  • 4
    \$\begingroup\$ That's not what the comma does. It appends a space instead of a newline. \$\endgroup\$
    – xsot
    Commented Oct 30, 2015 at 1:00
  • 2
    \$\begingroup\$ could use ␤ to indicate a semantically-important newline \$\endgroup\$
    – Eevee
    Commented Nov 1, 2015 at 2:02
11
\$\begingroup\$

Batch, 9 8 Bytes

@type %0

Saved a byte thanks to @Joshua

\$\endgroup\$
1
  • 4
    \$\begingroup\$ You can save a byte by eliminating the trailing %. \$\endgroup\$
    – Joshua
    Commented Oct 30, 2015 at 4:02
9
\$\begingroup\$

AutoIt, 34 bytes

Outputs itself to the clipboard:

ClipPut(FileRead(@ScriptFullPath))
\$\endgroup\$
9
\$\begingroup\$

Ruby, 14

$>.<<IO.read$0
\$\endgroup\$
1
  • 1
    \$\begingroup\$ Nice use of . to avoid parentheses \$\endgroup\$
    – Cyoce
    Commented Jul 3, 2017 at 6:21
8
\$\begingroup\$

Go, 111 105 bytes

package main
import("io"
."os"
."runtime")
func main(){_,p,_,_:=Caller(0)
f,_:=Open(p)
io.Copy(Stdout,f)}

My first code-golf in Go – just a few tricks you can use here I guess.

\$\endgroup\$
3
  • \$\begingroup\$ There is already an answer in Go - does this use the same method? \$\endgroup\$ Commented Oct 30, 2015 at 12:20
  • \$\begingroup\$ @VoteToClose: I realise it, I was inspired by the other one indeed, but used package renaming here (cheap trick) as well as different technique for opening and piping file to stdout. Saved me a massive 22 bytes ;-) \$\endgroup\$
    – tomasz
    Commented Oct 30, 2015 at 12:36
  • \$\begingroup\$ The method is actually a bit different, good one! \$\endgroup\$ Commented Oct 30, 2015 at 13:27
7
\$\begingroup\$

C, 49 bytes

s[];main(){read(open(__FILE__,0),s,48);puts(s);}

Edit: To clarify, the 49th byte is a newline.

This reads the source code minus the newline at the end to account for the newline which puts will append to the end of the output.

\$\endgroup\$
10
  • \$\begingroup\$ This code invokes undefined behavior twice. \$\endgroup\$
    – Joshua
    Commented Oct 30, 2015 at 4:03
  • 8
    \$\begingroup\$ Well, this is code golf. My code produces the desired output so it's a valid submission. \$\endgroup\$
    – xsot
    Commented Oct 30, 2015 at 4:16
  • 1
    \$\begingroup\$ @xsot In that case, you should probably list the compiler version + options; otherwise this might not be verifiable. \$\endgroup\$
    – Justin
    Commented Oct 30, 2015 at 7:16
  • 2
    \$\begingroup\$ If having undefined behavior is permitted as long as you can have some compiler that produces the desired output on some machine during some phase of the moon, then I propose int main(void) { *0; } as a solution. After all, the standard would permit an implementation that compiles that into a program that solves the problem. I'd be fine with using implementation-dependent behavior as long as you specify the compiler, but with undefined behavior, you can't even guarantee that you wouldn't get ten different answers if you ran that ten times in a row on the same machine. \$\endgroup\$
    – Ray
    Commented Nov 3, 2015 at 0:44
  • 2
    \$\begingroup\$ @MDXF I wasn't seriously suggesting that we write that solution. I was arguing against allowing undefined behavior. int main() {*0;} might work even on existing compilers, since it contains undefined behavior. Similarly, xsot's solution might work on existing compilers, since it contains undefined behavior. Neither one is guaranteed to solve the problem. (Although xsot's is admittedly more likely to do so, it might just as easily crash). My actual argument is that we should permit solutions that depend on implementation-dependent or unspecified behavior, but not undefined behavior. \$\endgroup\$
    – Ray
    Commented May 31, 2017 at 19:43
7
\$\begingroup\$

C, 31 bytes

main(){system("cat "__FILE__);}

The bash solution is so short, so why not base a C solution on it?

\$\endgroup\$
7
\$\begingroup\$

PowerShell, 39 36 31 25 Bytes

About as tight as I can get it:

gc $MyInvocation.MyCommand.Path | oh

Backed by popular demand this has been changed to:

gc $PSCommandPath|echo -n

prints to host shell current standard output.

\$\endgroup\$
7
  • \$\begingroup\$ gc $MyInvocation.MyCommand.Path is enough. It will automatically print it out. \$\endgroup\$
    – Andrew
    Commented Oct 30, 2015 at 0:44
  • \$\begingroup\$ its not guaranteed to especially if the script is running silently \$\endgroup\$ Commented Oct 30, 2015 at 0:49
  • \$\begingroup\$ Haha yea I don't care. I was going to post if no one else had a PowerShell answer. But I forgot that gc was an alias and was just going to use cat, so you had a byte on me there anyway. \$\endgroup\$
    – Andrew
    Commented Oct 30, 2015 at 0:51
  • \$\begingroup\$ Uh, I wouldn't be that strict about it. Otherwise every PS answer would explicitly have to pipe to the host shell, but that's up to you... \$\endgroup\$
    – Andrew
    Commented Oct 30, 2015 at 0:57
  • \$\begingroup\$ You could instead use gc $PSCommandPath for 17 bytes. The problem I see is that this spits out a newline (which doesn't exist in the source). It's ambiguous now if trailing newline is OK or not ... depending upon how that rules, we may need to do something tricksy like gc $PSCommandPath|write-host -n for 31 bytes. \$\endgroup\$ Commented Oct 30, 2015 at 13:03
6
\$\begingroup\$

Rust, 45 bytes

fn main(){print!("{}",include_str!(file!()))}

Try it online!

The file macro expands to the file it's invoked in's file path, the include_str macro expands to a string literal containing the contents of the file at the specified path, and the print macro prints.

\$\endgroup\$
0
5
\$\begingroup\$

Ruby, 15 bytes

$><<IO.read($0)

Source: https://stackoverflow.com/questions/2474861/shortest-ruby-quine

\$\endgroup\$
1
  • 13
    \$\begingroup\$ I've converted this to a community wiki because it isn't your own work. \$\endgroup\$
    – Alex A.
    Commented Oct 29, 2015 at 23:58
5
\$\begingroup\$

Pyth, 25 bytes

$import sys$h'e$sys.argv

This reads its file name. Essentially, it looks up argv, opens the file corresponding to its last argument, and prints its first line.

\$\endgroup\$
2
  • \$\begingroup\$ Can't you just do h'$__file__$? \$\endgroup\$ Commented Oct 29, 2015 at 23:34
  • 1
    \$\begingroup\$ @kirbyfan64sos That gives me the error NameError: name '__file__' is not defined. Pyth is compiled to Python, and then the resultant string is executed. So I wouldn't expect that to work. \$\endgroup\$
    – isaacg
    Commented Oct 29, 2015 at 23:41
5
\$\begingroup\$

Mathematica, 16 bytes

FilePrint@$Input

Run it in script mode.

\$\endgroup\$
1
  • \$\begingroup\$ I've been using Mathematica for many years and had never even heard of script mode. \$\endgroup\$ Commented Nov 13, 2015 at 18:04
5
\$\begingroup\$

><>, 13 Bytes

0:0go:c=?;1+!

Tested both on the online and offline interpreters. The g command is the closest to being able to read from the source file and if it doesn't count for the purpose of this challenge I'll mark my entry non-competing; I do believe it normally considered "cheating" for quines.

Try it online.

\$\endgroup\$
5
\$\begingroup\$

Haskell, 63 bytes

For science!

import System.Environment
main=getProgName>>=readFile>>=putStr
\$\endgroup\$
1
  • 1
    \$\begingroup\$ Only works with the runhaskell command. Very cool though \$\endgroup\$
    – HEGX64
    Commented Nov 2, 2015 at 22:44
5
\$\begingroup\$

Haskell, 49 bytes

{-#LANGUAGE CPP#-}main=putStr=<<readFile __FILE__

Try it online!

(GHC) Haskell has an extension to use the C preprocessor (commonly used for portability between versions and architectures.) Hopefully self-explanatory.

\$\endgroup\$
4
\$\begingroup\$

Go, 133 Bytes

Everyone clear? Go!

package main
import("fmt"
"io/ioutil"
"runtime")
func main(){_,f,_,_:=runtime.Caller(0)
s,_:=ioutil.ReadFile(f)
fmt.Print(string(s))}
\$\endgroup\$
1
  • 2
    \$\begingroup\$ This inspired me to write my own (and the very first) code-golf solution in Go. Looking for some general tricks, you can easily go down to 123 characters here by applying single-letter names for packages, for example r"runtime". \$\endgroup\$
    – tomasz
    Commented Oct 30, 2015 at 12:27
4
\$\begingroup\$

Node.js, 66 63 bytes

p=process;p.stdout.write(require('fs').readFileSync(p.argv[1]))

Doesn't use console.log, which appends a newline.

\$\endgroup\$
3
  • 2
    \$\begingroup\$ You can save a few bytes by using the synchronous api: p=process;p.stdout.write(require('fs').readFileSync(p.argv[1])) \$\endgroup\$
    – TehShrike
    Commented Nov 2, 2015 at 19:20
  • 2
    \$\begingroup\$ Why not console.log(require('fs').readFileSync(process.argv[1]))\n for 57 bytes? \$\endgroup\$ Commented Sep 30, 2016 at 0:14
  • 1
    \$\begingroup\$ This doesn't always work. Say the file is named test.js. It is valid to invoke it by running node test, which will cause this to throw an error. \$\endgroup\$ Commented Jan 10, 2017 at 11:35
4
\$\begingroup\$

Java 8, 133 125 Bytes (or 150 142 slightly cleaner)

Based on @VoteToClose's answer but choosing Files.copy and thus avoiding the intermediate String creation needed to call System.out:

import java.nio.file.*;interface A{static void main(String[]a) throws Exception{Files.copy(Paths.get(A.class.getName()+".java"),System.out);}}

or hard-coding the class-name even more:

import java.nio.file.*;interface A{static void main(String[] a)throws Exception{Files.copy(Paths.get("A.java"),System.out);}}

Cleaned up:

import java.nio.file.*;

class A {
    public static void main(String[] a) throws Exception {
        Files.copy(Paths.get("A.java"), System.out);
    }
}
\$\endgroup\$
3
  • \$\begingroup\$ Welcome to PPCG! (Programming Puzzles and Code Golf). Nice first answer! \$\endgroup\$
    – J Atkin
    Commented Nov 3, 2015 at 14:17
  • 1
    \$\begingroup\$ This is almost invalid, as we were told to not hardcode a filename. \$\endgroup\$ Commented Dec 5, 2015 at 0:28
  • \$\begingroup\$ You are not allowed to assume the file extension is .java. \$\endgroup\$
    – Makonede
    Commented Jul 9, 2021 at 20:43
4
\$\begingroup\$

HTML with JavaScript, 115 bytes (doesn't really count)

<!DOCTYPE html><html><title>x</title><script>alert(new XMLSerializer().serializeToString(document))</script></html>

Does this count? I don't mind, it was fun :)

Technically it doesn't open a file. It's also a well-formed HTML5 document. The XMLSerializer was the only tool which also returned the DOCTYPE portion, but is non-standard. Still, it works on chrome and firefox, and I bet other browsers.

And as a bonus:

JavaScript, 41 bytes

alert(document.currentScript.textContent)
\$\endgroup\$
6
  • \$\begingroup\$ Remove ";" at the end, save 1 byte :) \$\endgroup\$ Commented Jul 3, 2017 at 7:44
  • 1
    \$\begingroup\$ @ЕвгенийНовиков You're right, not sure why I left that in back then. It seems like I didn't count it though. \$\endgroup\$
    – Domino
    Commented Jul 4, 2017 at 11:07
  • 1
    \$\begingroup\$ You don't need the <title>x</title> \$\endgroup\$
    – Luvexina
    Commented Jul 8, 2021 at 21:21
  • \$\begingroup\$ @VFDan A well-formed standalone HTML document needs a title of at least one character, even if browsers will make do without it. I thought it was a nice bit of trivia to display in this silly answer. \$\endgroup\$
    – Domino
    Commented Jul 9, 2021 at 6:39
  • 1
    \$\begingroup\$ @Somebody Nope. The head element implicitly begins when a tag that should be inside the head is encountered, and the body implicitly begins when a tag that is only allowed in the body and not the head is encountered. Even the html tags are optional, I guess I didn't know that in 2015. Though you should probably always put the opening html tag so you can specify a lang attribute. \$\endgroup\$
    – Domino
    Commented Dec 9, 2023 at 4:56
4
\$\begingroup\$

𝔼𝕊𝕄𝕚𝕟, 2 chars / 6 bytes

ℹ⬮

Try it here (Firefox only).

The ℹ function both returns and pushes to the stack the source code. There is automatic outputting, so the contents of the stack will be outputted. Therefore, the source code will be outputted.

\$\endgroup\$
6
  • \$\begingroup\$ Does this read the source file, or a copy of the source code? \$\endgroup\$
    – lirtosiast
    Commented Oct 30, 2015 at 1:59
  • \$\begingroup\$ Here's the line in the interpreter source with the function. It's not really a file-based interpreter, but it reads the textarea value (aka the code). \$\endgroup\$ Commented Oct 30, 2015 at 2:31
  • \$\begingroup\$ You made this change an hour ago. Would your code have worked with the previous version? \$\endgroup\$
    – Dennis
    Commented Oct 30, 2015 at 2:47
  • \$\begingroup\$ @Dennis I actually made that change before seeing this challenge. It was because I didn't like the original output format. \$\endgroup\$ Commented Oct 30, 2015 at 2:53
  • 3
    \$\begingroup\$ @molarmanful Nevertheless, according to site policy, this is a noncompeting answer due to the fact that it uses a version of your language created after the challenge was posted. \$\endgroup\$
    – Doorknob
    Commented Oct 30, 2015 at 3:03

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.