Skip to main content

CRASM is ... well ... letslet's say frugal - and works more or less along a C like-like expression syntax. And as with C, there are no seperateseparate operators for low/high byte of an address. So

>label needs to become (label >> 8)

while

<label is to be changed to (label & $FF)

(theThe last can, AFAIK, be obmittedomitted - but keeping it makes it way more readable).

CRASM is .. well ... lets say frugal - and works more or less along a C like expression syntax. And as with C, there are no seperate operators for low/high byte of an address. So

>label needs to become (label >> 8)

while

<label is to be changed to (label & $FF)

(the last can, AFAIK, be obmitted - but keeping it makes it way more readable)

CRASM is ... well ... let's say frugal - and works more or less along a C-like expression syntax. And as with C, there are no separate operators for low/high byte of an address. So

>label needs to become (label >> 8)

while

<label is to be changed to (label & $FF)

(The last can, AFAIK, be omitted - but keeping it makes it way more readable).

Source Link
Raffzahn
  • 236.1k
  • 23
  • 682
  • 976

CRASM is .. well ... lets say frugal - and works more or less along a C like expression syntax. And as with C, there are no seperate operators for low/high byte of an address. So

>label needs to become (label >> 8)

while

<label is to be changed to (label & $FF)

(the last can, AFAIK, be obmitted - but keeping it makes it way more readable)