LOLCODE programming language

• Official Referrence of LOLCODE⁠

This image is a part of esolang-box 2.4.0⁠.

About

esolang-box project⁠ aims to provide easy and normalized interface for many (currently 227 (!)) programming languages by Docker, especially to uncommon esoteric programming languages⁠.

The implementation and interpreter of language LOLCODE is included in this image and can be invoked by the simple one command lolcode. (it's also an alias of script command, so you can use either.)

This script accepts standard input as the input of program and the first argument as program code file. The output of the script will be printed into standard output. This convension is shared between all esolang-box images, so you can use another language easily.

Usage example

Run a single LOLCODE script

Supposing you have hello world script hello.lolcode in the current directory like this:

$ cat hello.lolcode
HAI 1.2
  CAN HAS STDIO?
  VISIBLE "Hello, World!"
KTHXBYE

You can execute it with the following command:

$ docker run --rm -v "$PWD":/code:ro esolang/lolcode lolcode /code/hello.lolcode
Hello, World!

Processing input

$ docker run -i --rm -v "$PWD":/code:ro esolang/lolcode lolcode /code/hello.lolcode < input.txt

Debug code with shell

$ docker run -it --rm -v "$PWD":/code:ro esolang/lolcode sh
# lolcode /code/hello.lolcode
Hello, World!

Observing usage of exec syscalls

esolang-box 2.4.0 supports tracing of execve and execveat syscalls by strace command. Setting STRACE_OUTPUT_PATH environment variables and enabling ptrace will produce strace log to the specified path.

$ docker run --cap-add=SYS_PTRACE --rm -v "$PWD":/code --env STRACE_OUTPUT_PATH=/code/strace.txt esolang/lolcode lolcode /code/hello.lolcode
Hello, World!

Some considerations:

• Enabling ptrace breaks seccomp filter before kernel 4.8.⁠ You should be very careful to use --cap-add=SYS_PTRACE (especially you must not use it with Xenial).
• Using strace costs a huge performance overhead and syscalls may be 10x slower.