Did you ever wake up and think "FORTH is just too
darn easy -- I need a *real* challenge"? Straight
from Prfnoff himself, I present to you the BAK
programming language...

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

BAK: It's Not Forth

The only source file extension BAK recognizes is ".bak"
(or ".BAK"), and the BAK interpreter enforces this. This
guarantees some confusion with automatically generated
backup files.

The only data type in BAK is the pointer, but it shall be
referred to as the 'BAKword'. Every BAKword points to a
character, but it shall be referred to as the BAKword's
'reverse'. These BAKwords are kept on a data structure
called the 'LIFO'.

The position starts at the first reverse of the program.
After executing the feature at the position, the position
is incremented unless the feature otherwise specifies. Data
space is identical to program space.

On Tue, 12 Aug 2008 20:59:42 +0000, Guy Macon wrote:

Wow, add the BAK authors to the list of those Desperately Needing To Get
A Life

Many things look better than the code of BAK

A few simple definitions are

* DUP = SI SO BA SO
* EXIT = RI SI BA SO
* CLC = LIT 0 DUP FA BA BO
* XOR = CLC SI DI BA SO
* NOT = LIT -1 BA XOR
* (LIT) = RI SO RI FA RO SE SWAP SI RO EXIT
* 0BRANCH = NOT DUP LIT 1 FA SI SU (LIT) GO RI RO EXIT

These are compact definitions, (except for 0BRANCH) and many pairs and
triplets of instructions would be defined for greater factoring.

What is its unique selling point?

More closely resembles SK machine?

cheers
jacko

jacko wrote:

BAK was created purely for entertainnent value.

Take a look at these:

http://compsoc.dur.ac.uk/whitespace/
http://catseye.tc/projects/befunge93/doc/befunge93.html
http://www.lscheffer.com/malbolge.shtml
http://www.madore.org/~david/programs/unlambda/#what_is
http://esoteric.sange.fi/orphaned/bak/BAKref.txt
http://www.catb.org/~esr/intercal/

How did you manage to forget Brainfuck?

http://esolangs.org/wiki/Brainfuck

Virtually,
Michael Morris.

morrimichael@gmail.com wrote:

I ommited it because I don't like the name.
I don't like the name because it triggers spam filters.

Hmmm. Microsoft Viagra++ has a nice ring to it...

Brad Eckert wrote:

I work mostly with firmware...

What really made the Microsoft Viagra++ project go limp was the
customers. They seemred to have a problem buying such a product
from a company with "Micro" and "Soft" in the name. That and
the well-known performance issues.

On 26 Aug, 08:23, Guy Macon <http://www.GuyMacon.com/> wrote:

There seems to be too much focus on how hard it is. A little more
thought should be given to the end user experience ;-)

jacko wrote: