From: troy silvey (tbsilvey_at_juno.com)
Date: 2001-01-08 00:35:30
>example, use the following macros:
>
> #define CLI() __asm__ ("\tcli");
> #define SEI() __asm__ ("\tsei");
>
>To protect the increment of a variable (maybe because it's a word
Ok that makes sense now. But when I use the following definition,
the compiler tells me I have too many characters.....
#define CLS() __asm__("/tjsr/t$e544"); //C64 clear
screen routine//
In the html docs you have a longer literal string in one of the funtion
calls.
#define hi(x) (__AX__=(x),asm("\ttxa\n\tldx\t#$00",__AX__)
Is there a difference, or am I still doing something wrong?
>The asm syntax will probably change for the next release, because the
>current syntax is not flexible enough. Apart from that, the input should
get
>preparsed by the compiler to adjust it to the format expected by the
backend.
If your writing cross platform code it probably isn't the best way to
go.
But it seems the perfect tool when you want to used machince specific
kernal calls.
troy
________________________________________________________________
GET INTERNET ACCESS FROM JUNO!
Juno offers FREE or PREMIUM Internet access for less!
Join Juno today! For your FREE software, visit:
http://dl.www.juno.com/get/tagj.
----------------------------------------------------------------------
To unsubscribe from the list send mail to majordomo_at_musoftware.de with
the string "unsubscribe cc65" in the body(!) of the mail.
This archive was generated by hypermail 2.1.3 : 2001-12-14 22:05:38 CET