|
Top-level
 Some of the things that changes is that it standardize the coding style, type-awareness makes it so different types of data are displayed differently, that I never have to touch the formatting, that I can have assembly errors and hints appear directly in the IDE rendering. In the video above, I can't break away from the formatting by adding linebreaks. Suffixing a labels with -bin, -txt, -icn -chr will render the body of the label differently. 13 comments
@neauoire could you integrate the symbols file into the ROM format, so that source code can always be recovered? (obviously, the symbols can always be stripped, but it would give a clear indication of the expectation of openness) @thamesynne I could yeah, also I think it would be pretty safe to pad the symbols to 0x10000, it would just make roms that are mostly empty space, but wouldn't bread compatibility @thamesynne I'd pick some lz compression scheme that could easily be implemented in uxntal ;) @neauoire lz4, maybe? pretty much any compression scheme will dispose of acres of white space @thamesynne yeah I was thinking something like that. I took at stab at an implementation once but it kicked my butt. I'd have to try again @neauoire might also be useful to look at Einar Saukas' Spectrum-targeted compression algorithms - although they're more concerned with decompression size and speed, assuming a "grown up" computer will throw billions of cycles at the compression  @mpcnat I'm glad you've enjoying these little experiments :) I'll keep poking at this a bit further. |
Gregory's Server
This means that would I loose a source file, I can recover the sources from the rom and the symbols file and resume working on a project.