-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Timothy Miller wrote: > On 7/10/06, Hamish <[EMAIL PROTECTED]> wrote: > >>> NOOP.vh >>> >>> Is that good, or would that confuse people, since it's the same >>> >> syntax >> >> Actually calling it a NOOP confuses me... NOOP to me means >> increment the program counter. Do nothing else. Affect no other >> flags... Why separate by a .? Why not something like >> >> ASSERT v,h >> >> It's clear, does what it says on the tin. etc. > > I see your point, but at the same time, all instructions assert > flags. It's just that the NOOP does nothing BUT assert flags. See? > :) >
Yes, but AFAIK on any other architecture, it doesn't. I know we're arging semantics here, and it's not even hardware really, but NOOP's have always been described as NO OPERATION. Including setting/resetting flags. To redefine what a NOOP is, even for a private architecture like this.. It just doesn't feel right... [deleted] >> >>> >>> CALL.rvh 40(200) >>> >>> Or would that confuse people, making them think it's an offset? >>> >> >> Maybe something like [EMAIL PROTECTED] (The syntax reminds me of a till >> then. 40 items @ 200 :) > > Hey, I like that! Ah! I'm useful at last :) Hamish. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFEs1JD/3QXwQQkZYwRAhWVAKDWwmn8b5BA+X0bUx33Ujd26PfG5QCgm3io 2t5GFSaUsPS6kx4LkyK9Zoc= =o295 -----END PGP SIGNATURE----- _______________________________________________ Open-graphics mailing list [email protected] http://lists.duskglow.com/mailman/listinfo/open-graphics List service provided by Duskglow Consulting, LLC (www.duskglow.com)
