Will help you in a very limited way. Unfortunally, you will need to hunt from several places to go after any half-decent implementation of any decent-enough language.<p>But do anything first. So, take this tutorial and complete it. If after it you wanna move...<p>I&#x27;m working in my own language, and after read like hundreds of links&#x2F;blogs&#x2F;books&#x2F;etc, you will find that a lot of that is heavily biased torwards parsing, LISPys, FORTHs, and ultra-heavy-monads-worship or academic complexting that will make your head spin. After all that read, I&#x27;m still confused. Because a lot of things are not simpler or obvious in the way how make a blog or a ecommerce site can be.<p>So, read a part of the list I have collected:<p><a href="https:&#x2F;&#x2F;www.reddit.com&#x2F;r&#x2F;coding&#x2F;comments&#x2F;2ocw2r&#x2F;how_to_create_a_programming_language&#x2F;cmy71xn" rel="nofollow">https:&#x2F;&#x2F;www.reddit.com&#x2F;r&#x2F;coding&#x2F;comments&#x2F;2ocw2r&#x2F;how_to_creat...</a><p>----<p>Syntax is very important, but after read a lot, I think that do the parsing stuff is not the very best <i>first</i> step.<p><i></i>INSTEAD DO THE AST WALKER<i></i>. Seriously. Get clear how the the AST can be processed and focus in that. Changes in the AST will cause heavy impacts in your parsing stuff, and a lot of question need to get clarified first. For example, from the link above:<p><pre><code>    My first questions? How make a REPL, a debugger, how implement pattern matching, type checking, if a interpreter can be fast enough, if possible to avoid to do a whole VM for it, etc...

    Exist a LOT of practical questions that are left as &quot;a exercise for the reader&quot; that need clarifications.
</code></pre>
So, my advice:<p>- Get a list of what do you want for your language. Then think harder and try to remove features and get to the core of it.<p>- From the above, start to understand the details. For example: I wanna to do GO-style concurrency, so... how implement GO-style concurrency? If that is not solved, your syntax is pointless. That is why try to fill the &quot;core&quot; of the language as much as possible before to commit to the GUI (aka:syntax) of it.<p>- Then do a interpreter. Is FAR easier. Even if you wanna do a compiler, start here is more easier.<p>- On the side, play with your syntax, and imagine how write in the language could be. Then start to think &quot;to make this syntax do that, how I can do inside the guts of the compiler&quot;? But you can delay the parser for a while.<p>When the time come for the parsing, probably is better to do as a top-down parser and&#x2F;or pratt-parser. I don&#x27;t waste time with parser generators. If your disagree, ok with me ;)<p>I have find that use F# is great for this stuff. However, OCalm have more code-samples (ie: ML languages are made for this!). Lisp will work great if your are insane to like that ;). Hardcode C-developer? Tons of code to look, but not very much in clarity to see.