FORTH as intermediate ASM

It doesn't seem too uncommon for new languages that wish to be compiled to native code to first get translated into C, and then let gcc do the rest. Perhaps the best alternative to that right now is LLVM.

But why not FORTH? It probably won't be quite as optimized as gcc or LLVM could make it, but in most cases it would be Good Enough^TM. FORTH runs very close to the native code (even closer than C) and I can't imagine it being that hard to port the basic commands to a variety of platforms. But I only know the basic premise of FORTH, so there could be real issues that would make it impractical.

issues
if you have an issue - take a tissue. i dont mean it bodily liquids wise either. its very much on-topic

BBCode as intermediate ASM

This thread has outlived its usefulness and has been threadstopped. You can't reply anymore.

>>1
Because it wouldn't be as optimized as the code a C compiler produces. Forth is better than C because it provides working facilities for abstraction, and because its lesser performance is offset by the ability to write the routines which need to be fastest in assembly. Abstraction is pretty useless in a compiler target, since the compiler is the one who's writing the code, not you, and unless you're also going to write a native code compiler for your language (exactly the thing you're trying to avoid), you're just taking a performance hit for no reason. A high-quality Forth compiler could offset that somewhat, but as far as I know none of them are quite up to C performance.

This happens because in the main thread or in the thread that renders the
view/GUI and Events is used to open Socket. This should never be done not only
in java but in your source. I'm java developer that is why I know so much.
Please move this socket opening code to another thread and run it in low then
normal priority.

uncommon for new languages that wish to   burn much like   a knockoff version   of Brainfuck to   C is even   on the Brainfuck?