04-30-2003, 01:18 PM
Also, knowing asm is very useful even when using high level languages. You'd think compilers generate stable code, but that's not always the case with for instance watcom or borland. By dissasembling it i can see exactly what it does and find out where the bug is.
Or when i'm trying to get a certain loop to run as fast as possible, i usally tinker with the loop and dissassemble it until i find a code the makes the compiler generate as good code as it can (which always suxs pretty much).
Knowing asm makes a better high level coder as well, since you know how the computer works you know how to code optimal code.
So i don't agree, it will always be important. There's a huge difference between knowing asm and being good at it. DQB is the perfect example of why some people should just stick to compilers.
Or when i'm trying to get a certain loop to run as fast as possible, i usally tinker with the loop and dissassemble it until i find a code the makes the compiler generate as good code as it can (which always suxs pretty much).
Knowing asm makes a better high level coder as well, since you know how the computer works you know how to code optimal code.
So i don't agree, it will always be important. There's a huge difference between knowing asm and being good at it. DQB is the perfect example of why some people should just stick to compilers.
oship me and i will give you lots of guurrls and beeea