4 ms·

One pair of students decided to create a stack-based language. I guess they noticed it would save several lines of code and make the interpretation process easi

by dovyski 15y ago

One pair of students decided to create a stack-based language. I guess they noticed it would save several lines of code and make the interpretation process easier to do.

sounds 15y ago
I see you have other students use the language at the end. If you have a chance, it might be a rare opportunity to point out some of the innovative ideas, after all the projects are done.
- dovyski 15y ago
  Yeah, it's true. I will try to analyze and discuss the implementations at the end.
  - LeonidasXIV 15y ago
    Could you keep us updated about that? Such a round-up post with interesting ideas could be marvelous!
    - dovyski 15y ago
      Sure, I will blog about that in the future. Stay tuned :)
gliese1337 15y ago
The second thing I did after finding out about FORTH (after boggling for a bit and trying to figure out how the heck it worked without function arguments) was to go and design a stack-based language and implement an interactive interpreter for it in JavaScript. Largely just because I realized FORTH is so simple, I actually could do it. Then my language design aspirations languished for about 10 years until I had a Discrete Mathematics class based around writing a parser and interpreter for Datalog (subset of Prolog). Then there was the programming language design class where we implemented interpreters for various language features in Racket, but by then I forgot most of how to write parsers and (read) takes care of most of the hard part there. It certainly would've been more fun if we'd had to design our languages, rather than just implementing predefined ones. And several computer architecture & an operating systems class that dealt with "this is what C code gets turned into", but no details on the actual process of doing the translation. So, I guess this kind of thing has been fairly well represented in my formal education, but not very well integrated. Just disjointed bits and pieces as they're relevant for some other subject. It'd definitely be nice if they were more coherent earlier on, before tackling Compilers head on.

by dovyski 15y ago

One pair of students decided to create a stack-based language. I guess they noticed it would save several lines of code and make the interpretation process easier to do.

sounds 15y ago

I see you have other students use the language at the end. If you have a chance, it might be a rare opportunity to point out some of the innovative ideas, after all the projects are done.

dovyski 15y ago
Yeah, it's true. I will try to analyze and discuss the implementations at the end.
- LeonidasXIV 15y ago
  Could you keep us updated about that? Such a round-up post with interesting ideas could be marvelous!
  - dovyski 15y ago
    Sure, I will blog about that in the future. Stay tuned :)

gliese1337 15y ago

The second thing I did after finding out about FORTH (after boggling for a bit and trying to figure out how the heck it worked without function arguments) was to go and design a stack-based language and implement an interactive interpreter for it in JavaScript. Largely just because I realized FORTH is so simple, I actually could do it. Then my language design aspirations languished for about 10 years until I had a Discrete Mathematics class based around writing a parser and interpreter for Datalog (subset of Prolog). Then there was the programming language design class where we implemented interpreters for various language features in Racket, but by then I forgot most of how to write parsers and (read) takes care of most of the hard part there. It certainly would've been more fun if we'd had to design our languages, rather than just implementing predefined ones. And several computer architecture & an operating systems class that dealt with "this is what C code gets turned into", but no details on the actual process of doing the translation. So, I guess this kind of thing has been fairly well represented in my formal education, but not very well integrated. Just disjointed bits and pieces as they're relevant for some other subject. It'd definitely be nice if they were more coherent earlier on, before tackling Compilers head on.