Jump to content

desertfish

Members
  • Posts

    650
  • Joined

  • Last visited

  • Days Won

    17

Posts posted by desertfish

  1. I guess I'm the odd one out 🙂  
    I'm using 64tass.  It's the cross assembler version of what used to be turbo assembler/ turbo macro pro on the C64 natively in the past. 
    It has a few nice features that I make use of in the code generation backend of the Prog8 compiler.  Like automatically rewriting branch statements into a jmp when the branch offset gets too large, or vice versa, and automatically eliminating unused code blocks.  It does lack a "linker" step so can't be easily integrated with code coming from elsewhere.

  2. Thank you for the feedback! 

    Yeah I'm glad the x16edit integration works as smoothly as it does, really kudos to you making it rom-able in the first place!

    The 'smart' a sounds like a good feature and easy to add. Likewise a + r should be easy to add as well, however, what should it use as a filename to save the program to?

    Label scopes is pretty hard right now because the file inclusion mechanism is based on just inserting (unparsed) lines verbatim into the parser. I haven't given it much thought to make it smarter. I don't know what ca65 does regarding to scopes.
    About your suggestion: that would quickly hit the max length of the symbol names right now. So that has to be increased quite substantially (say twice) but that would also limit the number of symbols that can be stored.  I have no idea what to expect about the number of symbols in large assembly files though, so this may not be an issue at all (or already is).

     

  3. The discussion above prompted me to check the behavior of my File based Assembler and yup, it failed to assemble LDA $0024,Y as well thinking it is LDA $24,Y which is an unexisting addressing mode.   This has now been fixed, but was an interesting case!

    • Like 2
    • Thanks 1
  4. On 5/9/2022 at 9:19 AM, TomXP411 said:

    If LDA $0024,Y is not assembling to $89 24 00 (or at all), that's an error.

    That should be opcode $B9 instead.

  5. I was able to build the web emulator successfully myself, however it didn't run because it stopped with a audio subsystem not initialized SDL error.

    I'm on Manjaro Linux and only had to install emscripten as additional package, then type make wasm

    After that it downloaded and built the dependencies automatically, generated a couple of web files including a big wasm file at the end. I also tried building the official r38 release that's on the forum and it had the same issue when actually launching the emulator. So it's an issue on my end, but the actual compilation is done without errors.  I know too little about emscripten to see where the problem lies.

  6. My goodness that 🇳🇱 Dutch layout.. is that official?  I can't for the life of me think of anyone here in the Netherlands actually using that layout.  I think everyone here is just using the default US layout (and usually on a keyboard with a small horizontal enter key, so the ANSI variant)

×
×
  • Create New...

Important Information

Please review our Terms of Use