Re: Why I stop attacking HLA

"randyhyde@xxxxxxxxxxxxx" wrote:

> By providing IF/WHILE/etc
> "macros" you allow the students to begin doing useful things on day
> one, mastering other concepts in assembly language (such as how to do
> simple arithmetic)

Is this "High Level Logic" or "Low Level Logic" or simple
illogical? Why do you need "IF/WHILE/etc" to do simple arithmetic?
To explain an add or sub instruction you need no "IF/WHILE/etc".
And when you explain the add/sub instruction then you also have
to speak about the flags.

> until they've gained enough experience to learn the
> underlying CMP/Jcc mechanisms so they can write assembly language the

And if they know the flags, which "experience" do they need to
understand "jump if carry flag is not set"?

> right way. But the bottom line is that before they finish the course,
> they are no longer using IF/WHILE/etc. in their assembly programs. They
> are writing pure assembly code at that point.

Instead of writing High Level Assembler code ("IF/WHILE/etc") from
the first day and "pure assembly code" at the last day, they could
start with "pure assembly code" from the first minute and at the last
day they would know anything about segment and paging tables, interrupts,
taskswitch and protection.
.

Relevant Pages

  • Re: Why I stop attacking HLA
    ... mastering other concepts in assembly language (such as how to do ... | to speak about the flags. ... |> are writing pure assembly code at that point. ...
    (alt.lang.asm)
  • Re: AT89S51/2
    ... Lodewicus Maas wrote: ... Assembly language is more complex and powerfull? ... access to more things, like processor status flags. ...
    (comp.arch.embedded)