Nicolaas Groeneboom

This one is *extremely* difficult to optimise, as the internal optimiser isn't at all built for this kind of optimisation. The reason: TRSE doesn't *know* what STA $1234 contains, if...

hm I will need some more information here.. I created a small program that produces random numbers using your method (placing the variables at $02 instead of $00, since that...

ah I get it - the value gets stored in $00 since that is where you define your start position of the variables. However, i and j are optimised away...

Fixed! I simply added a tab "\t" at the start of the asm. Nobody in their right mind would start with a label here.. I hope

well you always have the asm(" ") option.. everything inside "" will be treated verbatim. Problem is that the parser doesn't "see" spaces or tabs.. hm.. I have to think...

I've been raking my head, but unfortunately I'm unable to come up with any good ways to fix this.. you can always put in a ";" as the first line,...

hmm interesting - I don't have any problems in VICE, but haven't tested on real hardware.. does it fail there? I wasn't aware of this bug, nice one! From the...

Hi, thanks for reminding me of this! The X16 hasn't been updated since I basically implemented basic support for it back in 2019, and the system has changed significantly since...

I've fixed up the X16 + started work on units and example files. There are currenlty 4 working example files + two units (Screen and Memory), and i've removed the...

I don't think TRSE cares about that right now - but since I'm moving all libraries to actually being written *in* TRSE, keeping up with the hardware changes should be...