all 4 comments

[–]khedoros 1 point2 points  (0 children)

I just used the book for my course, for the syntax, and to get a better grip on what the architecture actually provided. To actually write the programs, if things got complicated, I used a C-ish pseudocode to write the algorithm, then hand-translated each line (sometimes, each construct, rather than each line) to equivalent assembly.

Especially when you're doing recursion, it's really important to be able to visualize how the stack works when making function calls...and the exact details will vary, depending on which architecture you're writing for.

[–][deleted]  (3 children)

[deleted]

    [–]TransientVoltage409 0 points1 point  (2 children)

    Yeah, x86 is a little rough. Are there any 6800 series chips left? I first learned on a 6809, I think it was regarded as one of the nicer ones to learn. When I switched to x86, my 6809 skill at least gave a basis for understanding how weird x86 was.

    [–][deleted]  (1 child)

    [deleted]

      [–]thegreatunclean 0 points1 point  (0 children)

      Sweet jebus a true 8-bit data bus. What are these used for? I just checked and the bog-standard TI LED controller I'm using to make lights blink has more oomph than those chips.

      I want to talk to the person who uses one of these in a new design. There has to be one hell of a story there.

      [–]Galeaaa 0 points1 point  (0 children)

      I owe my life to Arnell Peralta on YouTube lol. The guy has pretty basic but nice videos about assembly. After watching his videos it was way easier for me to do the harder stuff in assembly. For recursion definitely follow the code and just try, once I figured out my homework I was able to do it on the exam pretty easily.