INRAC, the langauge RACTER (<a href="http://en.wikipedia.org/wiki/Racter" rel="nofollow">http://en.wikipedia.org/wiki/Racter</a>) has the most bizarre flow control I've ever seen in any computer language, ever. It can best be described as "a random, pattern matched GOTO/GOSUB" which is the most succinct description I can come up with.<p>I have a blog entry about it (<a href="http://boston.conman.org/2008/06/18.2" rel="nofollow">http://boston.conman.org/2008/06/18.2</a>) but in short, each line of an INRAC program (unless it ends with a '#' mark in which case execution continues to the next line) is a subroutine, each with a label. The label does not need be unique, but when you "call" a subroutine, INRAC will just pick one line with that label at random to execute. The pattern matching comes in because you can select the label with wildcard characters (which just picks a line that matches the pattern at random).<p>There isn't much about the language on the Internet. In fact, the <i>only</i> other page aside from my blog entry (which I wrote as I went through the existing source code I found for Racter) is the Racter FAQ (<a href="https://groups.google.com/forum/#!topic/rec.arts.int-fiction/RTV5CUkJ8fs" rel="nofollow">https://groups.google.com/forum/#!topic/rec.arts.int-fiction...</a>) which has a few inaccuracies (or perhaps was looking at a version of the code before processing).