0 Members and 1 Guest are viewing this topic.
but isn't brainf*ck supposed to be bare-bones and really hard to use?IMO, adding that stuff would kinda ruin the point
Quote from: turiqwalrus on October 07, 2011, 08:45:41 ambut isn't brainf*ck supposed to be bare-bones and really hard to use?IMO, adding that stuff would kinda ruin the point It'd still be ridiculously hard to use. The difference would be that you could actually make stuff with it. I support this.
true...a lack of for loops limits it ALOT...
++++[>+<-] is equivalent to For(4){+}
It'd still be ridiculously hard to use. The difference would be that you could actually make stuff with it. I support this.
Also, using goto makes conforming to the original BF spec very difficult because it's difficult to confirm that each open bracket has a closing bracket.
The only things brainf*ck requires (do we actually need to censor this here at Omnimaga?) is subroutines.
What do = and ' do? If = copies the value at the byte pointed to by the current memory cell into the current memory cell, then I think it's an excellent addition to the language
Quote from: JustCause on October 07, 2011, 09:03:03 amIt'd still be ridiculously hard to use. The difference would be that you could actually make stuff with it. I support this.I'd like to point out that BrainF*ck is turing-complete. What this means is that anything that can be done on any modern computer, can be done in BrainF*ck.If you had a lot of time to spare, it is, by definition, possible to factor the Nspire OS key using only BrainF*ck.
QuoteThe only things brainf*ck requires (do we actually need to censor this here at Omnimaga?) is subroutines. Using goto will effectively allow for subroutines to be written. I'll just have to have a return command.