Golfrun is stack based language and a C interpreter for that language, derived from GolfScript (but not fully compatible with).

Why Golfrun?

GolfScript is born to win golf code contests. The official interpreter is written in Ruby and proved to be rather slow in a golf contest I've read on Stackoverflow (3 minutes for the shortest solution).

Golfrun is born as a faster interpreter for GolfScript but soon, while I was writing it as quickly as I could, I've started changing the language.

Golfrun may be able to run some GolfScript sources without modification, but most of the time the code need to be adapted.

Why Golfrun is not an interpreter for GolfScript?

At some point while writing Golfrun, I've decided not to comply with the behaviour exhibited by GolfScript. There at least two reasons:

Is Golfrun usable in production code?

No. I am not spending efforts to make it reliable. Take it as a game, or a toy language, even if it is capable of doing real tasks.

Will Golfrun be improved/completed?

It will be completed and almost formalized some day! And several improvements are planned. But Golfrun is not a project I am spending too much time on!

Ok, show me something

This tutorial tries to show something about the language; there will be an almost formal documentation about all the operators and quirks.

It has this bug / I want this feature

You can contact me easily and of course you can use Sourceforge tools!