would learning assembly before C be a good idea? people say i shouldn't
waste my time but others say to do it to make learning C more understandable, what do you guys think?
Only if you deal with drivers, kernel or compilers.
>Assembly
>C anything
Do you have a vagina?
If the answer is no, your career is already over.
Google "highest employment rates" or kill yourself right now.
>>57892145
No. Assembly won't teach you anything more than C. Only learn if you have interest in low level stuff.
>>57892145
Learn C first, and then learn Assembly using C. It is the only way to better learning the two languages ;)
>>57892145
It's really nice to know if you're stuck on how pointers work.
That being said you really shouldn't have to go any more complex than a Z80 or a 486. If you want yourself looking at the developer guide for SSE4.1 you're doing it wrong.
>>57892145
what are yo looking to do with the knowledge? doing C will make you look at assembly at some point anyway
>>57892145
No, learn C first. Then you can see how assembly corresponds to C code. But you probably shouldn't bother learning assembly well enough to actually write it unless you have a specific reason to.
>>57893938
this
look at what your compiler turns your program into
>>57893938
machine code, the compiler turns c into machine code not assembly.
Learn C first. There's a lot of background information to learn before programming in assembly even begins to make sense. Moreover, C gives you portability, whereas there is a different assembly language for each CPU architecture (x86, ARM, PowerPC, etc...), and sometimes a different calling convention for each operating system on that architecture (i.e. on Linux, you can issue syscall instructions directly, while on Windows, you call into system functions in kernel32.dll, which in turn will issue a syscall).