3 ms·
Assembly language is usually an almost one-to-one correspondence with machine code instructions of the target architecture. Assemblers can build on that by prov
by WantonQuantum 5y ago
Assembly language is usually an almost one-to-one correspondence with machine code instructions of the target architecture. Assemblers can build on that by providing macros, etc but it's fundamentally about the programmer being aware of the instructions the CPU supports and using them to program.
I'm having trouble understanding the difficulty in the example. If "jnc" doesn't suit then there's "jc" to do the opposite.
If the difficulty is the conceptual leap to unstructured branching then I'd say that's what the teacher's job is - teach the students how to think about it.
- chillfox 5y agoCryptic names like "jnc" and "jc" is the huge hindrance in understanding it. It would be so much easier if it was just called what it did instead of an acronym. "jump_if_condition_is_met" or "jump_short_if_not_carry" (or which ever one it maps to) is much better and clearer than "jnc"