[EbonySeraphim]

[quote]Originally posted by Jeremy_Mc
actually, it is. it's just like ASM for an x86 processor. you tokenize it to byte code that is directly interpreted by the STAMP chip. i don't know how much lower you want to go, but i think i'm satisfied right where it's at.

I don't think we are on the right page with the definition of a low level language is. Low level means that the user types in code that is close to the machine level code - the lowest level being binary of course. Like in ASM you are dealing with very low level commands like mov, add, sub, push, and other basic commands that put you in control of nearly every processor cycle used in the program. C/C++ are high level languages because of high level functionality like:

CObj objectInst = new CObj(param1, param2);

I'm not calling you stupid, but if you don't know, what that code does automatically for you is create and initialize(in ASM declaring and initializing variables are seperate commands). During the initialization it has to call the function, first pushing its params on the stack, and depending on the calling convention, it might pop the params off itself or let the caller do it...I don't think I have to go on. I'm not trying to say "I'm a supernerd and know more than you" but that just what low level means.

i was born in 1985 and i have experience with most of that stuff. how dare you contest someone's knowledge you know nothing about. so what if you know everything under the sun about programming? that doesn't give you any right to do that. it's very possible for him to have done that. just becuase you didn't do it doesn't mean someone else can't.

Being born in 1985 is a bit different from 1987. 15-17 is quite a bit of a difference. I guess I did speak of something I knew nothing about, but intuition says that a 12 year old can't have a PhD. I know people can be young and know of certain things younger than most. But what he said would just take too much time for someone who just entered high school. Also, I gave other reasoning other than not believing it. Why did he just pop in her saying "I know blah blah blah and blah" and not talk about what he enjoys donig/currently is doing? Sounds like he was just trying to say "I'm the master."

aye a gung ho hardcore programmer i see. i'm not sure why you think that. i personally like an unbloated, stripped down language, but i don't want to spend time rewriting libraries full of functions just because the programmer who created the syntax decided it shouldn't be "nice".

I'm not that hardcore, but I would say I'm pretty devoted. The reason why you don't want some extremely high level language is because every application is different. When speed is crucial,(I'm speaking from a game development perspective here) you don't want some function that is supposed to "Clear Buffer" do something else automatically for you when it doesn't need to be there. You wasted cycles doing something you don't want it to. Also when you debug, its harder to find a bug when some command does so much stuff that the compiler doesn't give you an accurate line of where the problem is. ie. The problem is in call "InitializeGame()" - there is/should be so much stuff initialized in a game that you still don't know what to fix. As far as re-writing libraries, C/C++ has plenty stuff around that you don't have to do much coding if you don't want to deal with low level stuff. What I mean't by nothing has to be "nice" is that, when you want something to happen, it may take a lot of work, but if it was made nice for you, other stuff would be happening that you might interfere with what you really want.