Re: Re: [stella] DASM news

Subject: Re: Re: [stella] DASM news
From: "Andrew Davie" <atari2600@xxxxxxxxxxxxx>
Date: Mon, 24 Mar 2003 23:46:26 +1100
We can't just use the opcode... the address is important, too - we never
know what the programmer may be using it for, so the value *must* be
specifiable.  So whatever we choose, it's going to be OPCODE address.  Given
that we have to do that, it makes sense to give immediate eyeball
understanding to what the opcode *is*.  If it's a NOP, *call* it a NOP.

How about...

    NOP.b 0            ; a zero-page NOP
    NOP.w 0            ; an absolute NOP
    NOP 0                ; a normal NOP

the .b and .w extensions are familiar syntax, anyway.
If somebody wants to override these with macros - or we could have standard
macros, too - then, fine.
But they're still NOPs.  We should probably stick as much as possible with
the already-chosen names in the illegal opcode documentation that already


----- Original Message -----
From: <cybergoth@xxxxxxxx>
To: <stella@xxxxxxxxxxx>
Sent: Monday, March 24, 2003 11:28 PM
Subject: Aw: Re: [stella] DASM news

> Hi there!
> > BTW: ZOP?
> > What does the Z stand for? Zeropage? Don't forget NOP abs etc. then.
> Uhm... yes, certainly the zeropage. What for should "NOP abs" be needed?
> If you need a four cycle wait with two bytes you could as well use two
"stock" NOPs ;-)
> Greetings,
>      Manuel
> --------------------------------------------------------------------------
> Archives (includes files) at
> Unsub & more at

Archives (includes files) at
Unsub & more at

Current Thread