Robert Russell

@Nevada317 Actually I realized they do work as arguments to mnemonics, if that's what you mean. It's just as arguments to directives that they don't work, because we try to...

@bwack is right: the tiny1614 has what the [AVR Instruction Set Manual](http://ww1.microchip.com/downloads/en/DeviceDoc/AVR-Instruction-Set-Manual-DS40002198A.pdf) calls the AVRxt core, and no devices with this core are currently supported in AVRA. However, all the...

@ColonelPhantom It looks like someone got the ATmega4809 (an AVRxt device) working over at #40.

Sorry I was of no help, but I'm glad this isn't a problem for you any more. And thanks for pointing out some bugs in mnemonics.c, although I don't have...

I'll look into this more later, but I'm guessing it's because the internal representation of integers is more than 8bits, so when 128 gets inverted, the result isn't 127. For...

There's a comment related to this in the [usage file](https://github.com/Ro5bert/avra/blob/1b1b3fb0a3eddc5a3784ad301e3e060f6cb112de/USAGE.md): > The expression (~0x80) is a Bitwise Not operation. This operator returns the input expression with all its bits inverted....

You're not misusing it; `.undef` is currently not implemented (i.e., AVRA recognizes it, but does nothing). I'll look into providing an implementation for it.

@jameswilddev I planning on making it undefine any symbol (i.e., a combination of the preprocessor and assembler versions of the directive). Sometime before I started maintaining AVRA, the unfortunate decision...

I think my first comment from #34 pretty much applies here as well. I expect it will just work once you add a line to device.c. In any case, let...

Sorry for the late reply. I agree that outputting debug and EEPROM files by default is annoying. A semi-rewrite of some AVRA internals is underway, and I'll fix the `d`...