Just my 2c..

I learned x86 asm programming about 10 years ago, when it was just about the only way to get any speed into your graphics routines..

Several years later i switched to c, then on to c++.

I can''t begin to count the number of times that I''ve been grateful for my asm knowledge. At the moment when new processors come out in such a rapid rate (both CPUs and now programmable GPUs), sometimes you just have to write stuff in asm to be able to use the new functions; things like MMX (way back), SSE/SIMD (PIII) stuff, and now vertex/pixel shaders on the GF3.

Also, as someone pointed out before, it''s great being able to step through code at the assembly level, and even if you don''t know what''s going on straight away, you can always work it out..


Cheers,
Magnus

I''m just reading the Art of assembly, mainly so i can write faster game code and debug more easily. i think that the main reason i decided i was going to learn assembly was when my c++ code would make some strcat asm code screw up and i didn''t know what any of theat code meant!!

Well, I''ve started reading AOA too, so EEPROM, you don''t need to modify your code. I''ll use that as my first goal in learning ASM.

---

-Deku-chan

DK Art (my site, which has little programming-related stuff on it, but you should go anyway^_^)

Go on. You''re now entering the wondeful world of Low Level Programming.
Life of a coder is like a RPG. Only the good ones can reache the lowest level of the dungeon.

"Simple is beautiful"

Along time ago I thought about learning assembly but never did. After reading this thread , I''m convinced (like some others here). Good information.

"A man can''t just sit around." ''Lawn Chair'' Larry Walters (1982)

Won''t knowledge of VB be sort of outdated when VB.NET arrives?

...Anyhow, here''s a link for those interested in leaning assembly for windows:

http://win32asm.cjb.net

quote:

---

Original post by Anonymous Poster
its "assembly" you fucking idiots, the assembler assembles the assembly, get it?

---

Actually, you can use both words. Look it up in an online dictionary, you fucking idiot.

Twat.

---

"You say I''''m a bitch like it''''s a *bad* thing..."
Mail Site

well I''m sure most of what I''ve got to say has already been said here( didn''t realy bother reading most of it =)... I say take it... I wouldn''t pass it up for nothing... assembly is one hell of a language... yes it is hard to learn.... and I''d probably never use it to make anything bigger than say a pong game or something... just to much time involved... but its the only way to shave off that last few clocks on a function... or even if you don''t ever write a single line of assembly code in an actual program( beyond the learning ones)... the knowloge of the underlying hardware and and how it is most effecently used will allow you to make huge speed inhancements to your c/c++/other code.... or if your not interested in game program(if so why the hell are you here?) than it can also be used in the biz world... hardware drivers... OS programming and all kinds of other stuff =)

Just to say that assembly is lovely, besides optimization and knowing how the processor really works there''s another reason to learn it: FUN! And about that thing that only small things can be made in assembly I made an entire game called Punk (www.romanarce.com) 100% in assembly, 18000 instructions and it was FUN, of course it took 6 years (3/1994-5/2000) and now it looks like a game of 1994, obsolete, reason why I didn''t get any money at all, but it was great, and it''s not hard, after a while it becomes very easy and addictive.

Just for another perspective...(the VB programmer)...

I''d say learn both. It''s really easy to get a job as a VB Programmer (at least in the Dallas/Fort Worth Metroplex)...since it may be a while until you''re skilled enough with c++ and asm to make an entrance into the game programming world professionaly, you might want to have a backup plan. VB (and VB.NET) could help you by while you''re learning/lookin'' for game dev jobs.

Just some advice...

Epolevne