Writing a Forth in Haskell
reinvanderwoerd.nl
Writing a Forth in Haskell
1–10 of 55 posts
Re: Writing a Forth in Haskell
#2Surely you just take an existing LISP implementation and call "reverse" at the correct location in the code? :p
Re: Writing a Forth in Haskell
#3Doesn't really give Forth the credit it deserves. Totally misses the point of Forth: the simplicity of the environment and it's relationship to the underlying hardware, defining primitives like : and VARIABLE with CREATE and DOES>, threaded code, , (COMMA) , ... Nice promotion of Haskell though
Re: Writing a Forth in Haskell
#4Doesn't really give Forth the credit it deserves. Totally misses the point of Forth: the simplicity of the environment and it's relationship to the underlying hardware, defining primitives like : and VARIABLE with CREATE and DOES>, threaded code, , (COMMA) , ... Nice promotion of Haskell though
You're right of course, this is an ongoing exploration. I hope to learn the deeper truths in the process.
Re: Writing a Forth in Haskell
#5Doesn't really give Forth the credit it deserves. Totally misses the point of Forth: the simplicity of the environment and it's relationship to the underlying hardware, defining primitives like : and VARIABLE with CREATE and DOES>, threaded code, , (COMMA) , ... Nice promotion of Haskell though
You're right of course, this is an ongoing exploration. I hope to learn the deeper truths in the process.
Feel free to have fun with Haskell and Forth all you like. Your project. :) However, you need to learn C and/or ASM then implement Forth and some system codeto get to the deeper truths. Probably. Quite a bit of people using it in embedded systems.
Re: Writing a Forth in Haskell
#6I think it's also valuable to take a look at how Joy handles quoting program fragments. I just wish there were better online resources around the language.
Re: Writing a Forth in Haskell
#7Doesn't really give Forth the credit it deserves. Totally misses the point of Forth: the simplicity of the environment and it's relationship to the underlying hardware, defining primitives like : and VARIABLE with CREATE and DOES>, threaded code, , (COMMA) , ... Nice promotion of Haskell though
You're right of course, this is an ongoing exploration. I hope to learn the deeper truths in the process.
I would suggest re-doing the exercise on an 8 bit cpu with < 8 K of RAM. That will open your eyes to what is so special about Forth.
Re: Writing a Forth in Haskell
#8On an unrelated note, this is a pretty nicely designed website, OP.
Re: Writing a Forth in Haskell
#9Earlier quoted context omitted.
You're right of course, this is an ongoing exploration. I hope to learn the deeper truths in the process.
I would suggest re-doing the exercise on an 8 bit cpu with < 8 K of RAM. That will open your eyes to what is so special about Forth.
I'm curious about Forth, as it's probably the most important language I've never learned. I've done a fair bit of low-level, micro-optimised coding in C and assembly, but don't get much time for that kind of thing these days.
How would you describe Forth in relation to those? What makes it stand out and what are its weaknesses?
Re: Writing a Forth in Haskell
#10Earlier quoted context omitted.
You're right of course, this is an ongoing exploration. I hope to learn the deeper truths in the process.
I would suggest re-doing the exercise on an 8 bit cpu with < 8 K of RAM. That will open your eyes to what is so special about Forth.
One good place to look for that is " rel="nofollow">http://git.annexia.org/?p=jonesforth.git;a=summary>, previously discussed at " rel="nofollow">https://news.ycombinator.com/item?id=942684>.