Talk:Nope.

+ interpreter using Nope.

Ok, this is a pretty silly language, but it did make me laugh a bit. In an attempt to prove this language is not quite as useless as it looks, here is an interpreter for an existing, and arguably more powerful, esolang, +, using the provided Nope. interpreter:

xargs -n1 ./nope.exe < <(grep -oh + hello-world.+)

Where hello-world.+ is your attempt at Hello World in +, or any other valid + program. This probably won't work under Windows. Salpynx (talk) 07:21, 4 January 2019 (UTC)

Hello, World!

Continuing the silliness, here is a Hello World using the Nope. interpreter in the Linux shell. The interpreter returns status codes, this uses the $PIPESTATUS[@] array to collect the results. I spent far too long doing this... exploring exit status codes as output. This may be interesting for other languages. The similar language Nil is potentially flawed in this respect as it sets an success status despite claiming to do nothing. Salpynx (talk) 06:41, 5 January 2019 (UTC)

cmd="./nope.exe $(xxd -b -g0 <<< "Hello, World!"|sed 's/^.*: \([^ ]*\).*$/\1/'|tr -d '\n'|sed 's/^0//;s/0\|\(1\)/| .\/nope.exe \1/g;s/1/<:/g')"

echo -e "Lets run the following Nope. interpreter command chain:\n\n$cmd\n\n"
result=$(yes | eval "($cmd; echo "\${PIPESTATUS[@]}")2>/dev/null")
echo RESULT: $result

echo "Verify the PIPESTATUS results array using perl to convert binary to ASCII:"
echo $result | perl -lpe 's/[^10]//g,$_=pack"B*",$_'

Output

Lets run the following Nope. interpreter command chain:

./nope.exe | ./nope.exe <:| ./nope.exe | ./nope.exe | ./nope.exe <:| ./nope.exe | ./nope.exe | ./nope.exe | ./nope.exe | ./nope.exe <:| ./nope.exe <:| ./nope.exe | ./nope.exe | ./nope.exe <:| ./nope.exe | ./nope.exe <:| ./nope.exe | ./nope.exe <:| ./nope.exe <:| ./nope.exe | ./nope.exe <:| ./nope.exe <:| ./nope.exe | ./nope.exe | ./nope.exe | ./nope.exe <:| ./nope.exe <:| ./nope.exe | ./nope.exe <:| ./nope.exe <:| ./nope.exe | ./nope.exe | ./nope.exe | ./nope.exe <:| ./nope.exe <:| ./nope.exe | ./nope.exe <:| ./nope.exe <:| ./nope.exe <:| ./nope.exe <:| ./nope.exe | ./nope.exe | ./nope.exe <:| ./nope.exe | ./nope.exe <:| ./nope.exe <:| ./nope.exe | ./nope.exe | ./nope.exe | ./nope.exe | ./nope.exe <:| ./nope.exe | ./nope.exe | ./nope.exe | ./nope.exe | ./nope.exe | ./nope.exe | ./nope.exe <:| ./nope.exe | ./nope.exe <:| ./nope.exe | ./nope.exe <:| ./nope.exe <:| ./nope.exe <:| ./nope.exe | ./nope.exe <:| ./nope.exe <:| ./nope.exe | ./nope.exe <:| ./nope.exe <:| ./nope.exe <:| ./nope.exe <:| ./nope.exe | ./nope.exe <:| ./nope.exe <:| ./nope.exe <:| ./nope.exe | ./nope.exe | ./nope.exe <:| ./nope.exe | ./nope.exe | ./nope.exe <:| ./nope.exe <:| ./nope.exe | ./nope.exe <:| ./nope.exe <:| ./nope.exe | ./nope.exe | ./nope.exe | ./nope.exe <:| ./nope.exe <:| ./nope.exe | ./nope.exe | ./nope.exe <:| ./nope.exe | ./nope.exe | ./nope.exe | ./nope.exe | ./nope.exe <:| ./nope.exe | ./nope.exe | ./nope.exe | ./nope.exe | ./nope.exe <:| ./nope.exe | ./nope.exe | ./nope.exe | ./nope.exe | ./nope.exe <:| ./nope.exe | ./nope.exe <:| ./nope.exe 

RESULT: Nope.0 1 0 0 1 0 0 0 0 1 1 0 0 1 0 1 0 1 1 0 1 1 0 0 0 1 1 0 1 1 0 0 0 1 1 0 1 1 1 1 0 0 1 0 1 1 0 0 0 0 1 0 0 0 0 0 0 1 0 1 0 1 1 1 0 1 1 0 1 1 1 1 0 1 1 1 0 0 1 0 0 1 1 0 1 1 0 0 0 1 1 0 0 1 0 0 0 0 1 0 0 0 0 1 0 0 0 0 1 0 1 0

Verify the PIPESTATUS results array using perl to convert binary to ASCII:
echo $result | perl -lpe 's/[^10]//g,$_=pack"B*",$_'
Hello, World!

User: Salpynx, thanks a lot for actually taking a look at this language. I didn't think that anyone would see the page. There are a million other languages more interesting than this one, and I'm grateful that this is the language that made you laugh. Areallycoolusername (talk) 00:28, 7 January 2019 (UTC)Areallycoolusername

Cat program

It’s not possible to write cat in this language, as cat should echo every possible input, not just a carefully picked one. —arseniiv (talk) 13:24, 27 March 2019 (UTC)