Skip to content

Rough Book

random musings

Menu
  • About Me
  • Contact
  • Projects
    • bAdkOde
    • CherryBlossom
    • FXCalendar
    • Sulekha
Menu

bAdkOde

Translation into C

bAdkOde can easily be translated into C. Assuming that we have three (long int) variables called a, b, and top that refer to register a, register b, and top of the stack, and also assuming that we have two (long int) arrays mem and stack, we can translate bAdkOde into C via the following rules:

1. Any references to the registers a and b directly translate to the variables 
   a and b.
2. [b or [a translates to mem[b] or mem[a].
3. ) and ( both use stack[top]. However, in ), stack[top] is on the 
   right-hand side of the assignment expression whereas in ( it is on the 
   left-hand side.
4. >, +, and - map to =, +, and - respectively.
5. ', ", and ? map to printf (or printf("%d", value)), putchar (from stdio.h) 
   and getchar (also from stdio.h).
6. { maps to while, and =, !, +, and - map to == 0, != 0, >= 0, and < 0. } 
   maps to the closing } brace for the while.

Note: My current implementation (which I wrote around four or five years ago) really sucks! I think the interpreter could be written more elegantly. Also, I think I should probably figure out another way to implement the memory and stack in the C translation. Right now I create a fixed-size array. I think the ideal implementation would be a linked list that grows and shrinks as required.

Translation of fibonacci.bad into fibonacci.c
[sourcecode language=c]
#include

int main()
{
long int a = 0;
long int b = 0;

long int mem[131072];
long int stack[131072];

long int top = 0;
long int i = 0;

/* zero out memory and stack */
for(i = 0; i < 131072; i++) { mem[i] = 0; stack[i] = 0; } stack[top] = 0; top++; stack[top] = 1; top++; a = 10; mem[a] = a; while(mem[a] != 0) { top--; a = stack[top]; top--; b = stack[top]; stack[top] = b; top++; printf("%d", b); putchar(32); b += a; top--; a = stack[top]; stack[top] = b; top++; stack[top] = a; top++; a = 10; mem[a]--; } putchar(8); putchar(10); return 0; } [/sourcecode] Turing completeness and self-modifying code

I have no idea if bAdkOde is Turing Complete. I suspect it might be, but I have no proof. I recall reading somewhere that if you are able to write a quine (program that prints itself) in a language, then that language is Turing Complete. I figure that if I'm able to write a quine then I should be good! Regarding self-modifying code, I expect that it should be trivial to modify the interpreter so that program code exists in the same memory-space as data. However, this would make the translation of the program into C a little trickier.

Oh, and here is a link to the bAdkOde interpreter that I wrote in Perl (I'm not proud of this code at all! Could be written better :p).

Closing remarks

bAdkOde isn't meant to be a practical language. It's an esoteric language and its creation was an academic exercise for me. If you're trying to write actual software in bAdkOde, then God help you! 🙂

Pages: 1 2 3 4 5 6

4 thoughts on “bAdkOde”

  1. Steve O says:
    December 14, 2009 at 4:56 pm

    Ugh. Macros are the devil incarnate. Nothing makes grep-ing through large amounts of source code more painful than macros. Nice post though. I’m impressed with your use of EBNF and creative ability with new programming languages! This also lead me to look up several other esoteric languages (i.e. Brainfuck).

    Steve

    Reply
  2. vivin says:
    December 14, 2009 at 6:45 pm

    @Steve O
    Oh yeah, a large number of macros can make things really hairy. But I think that’s probably due to macro abuse! I made macros here just because that’s what I was familiar with when I was doing assembly programming. Then again, this isn’t meant to be a language for serious software projects! I’m glad you liked the EBNF and I’m also glad that you found bAdkOde creative. I guess all those theoretical computer-science classes I took at ASU weren’t for nothing! 😉 Haha!

    Esoteric programming languages are pretty neat. I think you realize how much you take for granted in high-level languages when you work with some of the more limited ones, like Brainfuck. On the other hand, they really make you think in novel ways and also completely change the way you approach problems. I think it’s a good thing.

    Reply
  3. Pingback: A bAdkOde quine (which proves that bAdkOde is Turing Complete) | Rough Book
  4. Pingback: A brainfuck interpreter in bAdkOde | Rough Book

Leave a Reply Cancel reply

Your email address will not be published. Required fields are marked *

Meta

  • Log in
  • Entries feed
  • Comments feed
  • WordPress.org

Archives

  • February 2023
  • April 2020
  • February 2020
  • January 2020
  • December 2019
  • November 2019
  • September 2019
  • August 2019
  • July 2019
  • June 2019
  • May 2019
  • March 2019
  • February 2019
  • January 2019
  • December 2018
  • November 2018
  • September 2018
  • August 2018
  • July 2018
  • June 2018
  • May 2018
  • April 2018
  • March 2018
  • February 2018
  • January 2018
  • December 2017
  • November 2017
  • October 2017
  • June 2017
  • March 2017
  • November 2016
  • August 2016
  • July 2016
  • June 2016
  • February 2016
  • August 2015
  • July 2014
  • June 2014
  • March 2014
  • December 2013
  • November 2013
  • September 2013
  • July 2013
  • June 2013
  • March 2013
  • February 2013
  • January 2013
  • October 2012
  • July 2012
  • June 2012
  • January 2012
  • December 2011
  • November 2011
  • October 2011
  • September 2011
  • July 2011
  • June 2011
  • May 2011
  • February 2011
  • January 2011
  • December 2010
  • November 2010
  • October 2010
  • September 2010
  • July 2010
  • June 2010
  • May 2010
  • April 2010
  • March 2010
  • January 2010
  • December 2009
  • November 2009
  • October 2009
  • September 2009
  • August 2009
  • July 2009
  • May 2009
  • April 2009
  • March 2009
  • February 2009
  • January 2009
  • December 2008
  • November 2008
  • October 2008
  • August 2008
  • March 2008
  • February 2008
  • November 2007
  • July 2007
  • June 2007
  • May 2007
  • March 2007
  • December 2006
  • October 2006
  • September 2006
  • August 2006
  • June 2006
  • April 2006
  • March 2006
  • January 2006
  • December 2005
  • November 2005
  • October 2005
  • September 2005
  • August 2005
  • July 2005
  • June 2005
  • May 2005
  • April 2005
  • February 2005
  • October 2004
  • September 2004
  • August 2004
  • July 2004
  • June 2004
  • May 2004
  • April 2004
  • March 2004
  • February 2004
  • January 2004
  • December 2003
  • November 2003
  • October 2003
  • September 2003
  • July 2003
  • June 2003
  • May 2003
  • March 2003
  • February 2003
  • January 2003
  • December 2002
  • November 2002
  • October 2002
  • September 2002
  • August 2002
  • July 2002
  • June 2002
  • May 2002
  • April 2002
  • February 2002
  • September 2001
  • August 2001
  • April 2001
  • March 2001
  • February 2001
  • January 2001
  • December 2000
  • November 2000
  • October 2000
  • August 2000
  • July 2000
  • June 2000
  • May 2000
  • March 2000
  • January 2000
  • December 1999
  • November 1999
  • October 1999
  • September 1999
©2023 Rough Book | Built using WordPress and Responsive Blogily theme by Superb
All original content on these pages is fingerprinted and certified by Digiprove