CodeWalrus

Development => Calculators => Calc Projects, Programming & Tutorials => Topic started by: JWinslow23 on March 24, 2016, 08:02:16 PM

Title: BF Interpreter because idk
Post by: JWinslow23 on March 24, 2016, 08:02:16 PM
I guess I'll leave this here with no explanation.
Title: Re: BF Interpreter because idk
Post by: Dream of Omnimaga on March 24, 2016, 08:31:41 PM
Is that in Axe? I think I recall @Juju making a BF interpreter in 2010, but it was in BASIC.
Title: Re: BF Interpreter because idk
Post by: Dudeman313 on March 24, 2016, 09:13:11 PM
Quote from: JWinslow23 on March 24, 2016, 08:02:16 PM
I guess I'll leave this here with no explanation.
I want an explanation!  :P
The title is somewhat self-explanatory, though.
Title: Re: BF Interpreter because idk
Post by: Ivoah on March 24, 2016, 09:31:21 PM
Someone also made a BF compiler for the CSE
Title: Re: BF Interpreter because idk
Post by: Dream of Omnimaga on March 24, 2016, 10:03:50 PM
Quote from: Dudeman313 on March 24, 2016, 09:13:11 PM
Quote from: JWinslow23 on March 24, 2016, 08:02:16 PM
I guess I'll leave this here with no explanation.
I want an explanation!  :P
The title is somewhat self-explanatory, though.
Brainf*ck is an interpreted programming language that isn't really meant to be programmed in, but rather was intended to make something much harder to decipher than assembly just for the sake of it.
Title: Re: BF Interpreter because idk
Post by: Snektron on March 24, 2016, 10:12:08 PM
I made a BF interpreter for Ti 84 + in assembly a while ago too. Always a fun little project
Title: Re: BF Interpreter because idk
Post by: JWinslow23 on March 24, 2016, 10:12:41 PM
Quote from: DJ Omnimaga on March 24, 2016, 10:03:50 PM
Quote from: Dudeman313 on March 24, 2016, 09:13:11 PM
Quote from: JWinslow23 on March 24, 2016, 08:02:16 PM
I guess I'll leave this here with no explanation.
I want an explanation!  :P
The title is somewhat self-explanatory, though.
Brainf*ck is an interpreted programming language that isn't really meant to be programmed in, but rather was intended to make something much harder to decipher than assembly just for the sake of it.
Actually, it was meant to be a Turing-complete language with the smallest compiler possible. The original designer got it down to 200 bytes iirc.

And no, it is not in Axe. Why would it even be in Axe?
Title: Re: BF Interpreter because idk
Post by: Dream of Omnimaga on March 24, 2016, 11:49:09 PM
Quote from: JWinslow23 on March 24, 2016, 10:12:41 PM
Why would it even be in Axe?
Because Axe is your main language? I think my question was a valid question.
Title: Re: BF Interpreter because idk
Post by: JWinslow23 on March 24, 2016, 11:51:27 PM
Quote from: DJ Omnimaga on March 24, 2016, 11:49:09 PM
Quote from: JWinslow23 on March 24, 2016, 10:12:41 PM
Why would it even be in Axe?
Because Axe is your main language? I think my question was a valid question.
How would you even take input for that? :P
Title: Re: BF Interpreter because idk
Post by: Dream of Omnimaga on March 24, 2016, 11:51:48 PM
Didn't Axe have an input command?
Title: Re: BF Interpreter because idk
Post by: JoeYoung on March 24, 2016, 11:52:48 PM
Isn't the whole point of the brainc compiler that it's only 200-300 bytes?
Title: Re: BF Interpreter because idk
Post by: JWinslow23 on March 25, 2016, 03:14:46 AM
Yes, JoeYoung. It is.