<p>This is an offer for those of you guys that are nerdy and passionate about programming. Ever since I was little (let’s say little = 14, which in retrospect seems more or less like the good ole times when we’d joke about how spooled DNA looks like white stuff…), I’ve always wanted to write my own assembler-interpretor suite (compiler) but never until this year have I acquired the necessary mindset to venture into this task. Now that I think I’m ready to tackle this monster, I want to extend an invitation to the rest of the (hopefully) creme de la creme of our generation to write yet another unoriginal yet satisfying language just for the sake of it.</p>
<p>I mean, come on, the last time I looked stuff up in a programming manual, all I got were pages after pages of dry documentation telling me what I couldn’t do because the developers “felt that it would be bad practice to allow” so and so or <em>insert generic excuse here</em>. Well, wouldn’t it be satisfying to tell the document to screw itself (obviously not literally) and patch in whatever it is that you need and force it upon the world? (it is, after all, your language)</p>
<p>In case any of you are interested, here are some technical information about the project.</p>
<p>The suite will consist of three a parser and an assembler, I’ve already prototyped the ASM in python and will later port it to C. Concepts borrow heavily from Python’s own bytecode walker:</p>
<p>The parser generates ASM and creates arrays of constants and object names
The ASM walker implements a primitive stack to interact with those objects, the stack can be later implemented as</p>
<p>
struct object{
void* ref;
int counts;
}
object* stack;
<p>I’ll be implementing the lexical parser later which will be where the real fun comes in, so if anyone’s interested in defining the grammar and syntax of the language, I’ll be happy to have you along.</p>
<p>Damn, that looks complicated lol. I have some experience with java, .NET and a few other random aspects of programming, but I’ve never done anything with the actual construction of a compiler.</p>
<p>Haha, good luck though. That’s a pretty impressive project.</p>
<p>I taught myself HTML and CSS and some JavaScript when I was 10-12
I made layouts and graphics in photoshop, coded them as layouts and used them in my own websites.</p>
<p>Shooting yourself in the foot with Java:
After importing java.awt.right.foot.* and java.awt.gun.right.hand.*, and writing the classes and methods of those classes needed, youve forgotten what the hell youre doing.</p>
<p>Hehe, I’d be happy to join this project. :D</p>
<p>I’ve learned a bit of Java in school and also studied some of the basics of Python, C and C++. I’m probably not as smart as you in terms of computer programming but I think this is an interesting project. In what ways would I be of assistance and how exactly will this work out?</p>
<p>dude the language is going to need to have some sense of order. if we just allow memory sizes of different data structures to be whatever size they feel like we’ll get corrupted memory faster than i could breathe air.</p>
<p>are you making it oop or not? it would be cool to make a fully oop language but this may stick you in the box that you seem so desperate to get out of lol</p>
<p>NiteStriker, do you even know anything about computer architecture?</p>
<p>can you give me the specifications on various RISC architectures? how is memory stored on the stack? in which order (high or low) do x86 processors store information? what register can be used to point to the next address to be used?</p>
<p>if you dont know those of the top of your head, making a compiler or assembler at your knowledge is somewhat laughable.</p>
<p>not meaning to be harsh, but thats reality. there are some great books on x86 architecture out there, amazon them if you are really interested</p>