K? Pŕo?ćtiόnŹ

As long as I've been programming compiler design and theory has always interested me. I used to read Jack Crenshaws compiler tutorial all the time, and before I really had any solid foundation I used to make the ****tiest little "interpreters" if you would even call it that in Liberty BASIC when I was first starting out in programming.

Jack Crenshaw I ****ing love you.

And even after having a "good" idea of what I was doing I still wasnt doing so hot code wise.

I would always just jump right into coding and do this and that and then a week later it was a ****ing mess and I would scrap the project. I always said I'll go back and clean the code up later and make this better and make that conform to that. But no, never did it. Just scrapped it.

A good and recent (somewhat recent) example of me doing this is http://www.gamethreat.net/forums/sta...0lhl-1-kc.html . I just added **** on **** on **** and it turned into ****.


So, I'm trying it again but this time trying to do it right. I've been thinking a good deal about how I want the language to be structured, what kind of types I want it to allow and how I'm going to handle them.

While I've been thinking about the language I've been working on accessories for the compiler itself like the editor, a few tools. Reading documentation, picking what assembler I'm going to use, resource compiler, etc.

*Note* if you ever need a syntax editor thats extremely easy to work with (code wise) I recommend RAEdit, its pretty awesome. Screenshot of the editor I implemented with it






I'll keep posting blogs whenever I make progress. beep. boop.