Problems using Integer.encode()

[pnin77]

Using openDLX, I encountered the following bug: A code line like src: .word 0xFFFFFF85 will, when assembled, lead to a ParserException with the Error message "expected number or label but got:0xFFFFFF85" This, as I found out, is due to a limitation of the Integer.encode() method used by the parser - Integer.encode() accepts only strings representing a positive integer value, which 0xffffff85 obviously isn't. Is this behaviour wanted ?

[smetzlaff]

Thanks for the report.

I'll check if .word values >0x7fffffff should be supported in the simulator back-end.