LÖVE

This started out as a small project in ROBLOX Studio, but since it was just core lua, I could easily port the code over and add stuff like console text input.

It's not perfect by a long shot. It seems that using a translator doesn't work, but this will (wasn't done by a translator):
+++++ +++++ [ > +++++ ++ > +++++ +++++ <<- ] >++. >+++++.

Line breaks also have to be removed since the command line seems to see them as a new input and runs each line as it's own input.

(also if you have no idea what brainfuck is, it's an esoteric language made for the purpose of having the smallest possible compiler. More info here: https://en.wikipedia.org/wiki/Brainfuck)

Hi, welcome to the forum. I don't quite get how it works. I don't see any print command (dot) in the program, yet the output is: The program doesn't generate 55 nor 2, so I wonder why does it print that.

Would be useful if you posted this along:
https://en.wikipedia.org/wiki/Brainfuck

Eh, 'tis simple but does the job. Congratulations!

I didn't include the . command since I just wanted to translate brainfuck code. I can easily add it if needed

What it basically does is print the complete memory stack, by checking that they are "valid" printable characters. Though that may be wrong because it just checks that the number is above 32 and not if the number is under a value, so if you try to print numbers above 255 you'll probably have errors.

One thing I consider you do wrong is filling the table at startup, that is not something you need, a 0 even though is 0 uses 64bits of memory so loading thousands of those inside a table for nothing is really a waste. As an example you could do: To icrement a cell, this allows the cell to be nil which doesn't consume memory like a 0 does.

Anyway, the program looks really nice, and can be easily extended which is cool, I would implement the dot though since that is what you expect brainfuck to do, I wrote programs to use two or three cells to write whole sentences which I can display with this interpreter.

Also you should delete all print statements that are simply for debugging, since those are confusing to the user running your interpreter

Added all Positive's suggestions and updated the OP.

That is great! I'm glad I could help, I downloaded the new file and had a look again and it was much better, so I decided to have some fun with it, first I must note that all the changes I made are TOTALLY UNNECESSARY! but if you find something you deem useful you can feel free to use it in your program.

So what did I do:

• Made the output a string instead of directly printing to the console
• I sandboxed the program, now it environment only contains string.char that is the only lua function the program needs.
• Made the program return the output string at the end so that you can print it or something (you could access it from the environment too but it is easier this way)
• Made a run function that runs the program with a hook that errors when the program is in an infinite loop, this is pretty useful for Brainfuck programs that have many loops and some of them may never return. The quota (number of instructions) can be passed as an argument to run if 10000 is too little.
• The returned function pcalls the run function so that the error doesn't propagate to the main program
• When a char is not recognized in the compilation step, instead of ignoring it I add a new line, this way errors, which commonly point to the line where the Lua error is, can be used to know what character in the Brainfuck program has the error, since Lua line == Brainfuck character
• In your program if you try to print a cell with a value of 1000 it completely crashes I fixed this so cells can only contain numbers up to 255 and if that value is exceeded they wrap to 0, this could be changed with some more work in the dot (making sure that the cell is a printable character or something like that).
• I removed some unused variables like BfString and utf8, and took the compile function outside of interpret so that it isn't generated every time interpret is called

The next step would be to implement input command (,) but that may be harder, anyway have fun!

You are all crazy.

Looks like it no longer violates the ENSI Brainfuck standard. Congratulations!