Is _asm{} as useful as i think it is? for example writing a function that passes it's parametersto _asm{} and then does some loops/if's etc then returns back. That would be more efficient (for mass/batch use) than if i wrote the function in C++ right?
>>3
lol yes because a decent compiler will optimise short bits of code to their equivalents in assembly. If you're going to prematurely optimise like this, you should do it with a substantial chunk of bottlenecked code.
Don't prematurely 'optimise' your code. 19/20 times, your compiler will probably do a better job.
Once you master x86 assembly, and C/C++, then you'll know what to use what for.
Though I could probably write quite a bit of my code in assembly, I know better than to do that.
I've only used assembly for hooking applications (I don't have the .exe source, but I do have the source to a .dll it loads, so I patch the memory at run-time and redirect flow into my .dll using assembly)
tl;dr if you should do it, you would *know* already
I've never gotten the point of inline assembly (except for platform-specific magic in system libraries); surely, you cannot write it as freely as you could if you wrote the whole program? The other registers must surely be troubled by the inline code messing things up?