Hello Ullrich, perhaps it would be enough to output a warning message, if the parser reaches an <> symbol after an .if statement. There is a workaround with brackets, which perhaps is better than making code with .if .. <> .. uncompatible. so it could read (a)<>(b) as a not equal to b, which could be the default and (a)<(>b) as a less than .hibyte(b) . With more complicates expressions: (a+b)<>(c+d) :not equal to or (a+b)<(>(c+d)) :less than hibyte . Greetings Carlos ---------------------------------------------------------------------- To unsubscribe from the list send mail to majordomo@musoftware.de with the string "unsubscribe cc65" in the body(!) of the mail.Received on Sat Mar 20 19:38:20 2004
This archive was generated by hypermail 2.1.8 : 2004-03-20 19:38:26 CET