Stefan Rueger

I piggy-backed onto PR #1059 [code](https://github.com/avrdudes/avrdude/pull/1059/commits/297740db0e078e90387507e849cb5a7b5ded2c09) to not list programmer ids that start with dot on `-c ?`. This is now symmetric with `-p ?`. I left `-c ?type` alone...

OK - I fixed the MacOS error and warning. I think. The errors we get now may be owing to a changed setup of how flex/bison is being provided for...

@mcuee Clearly, the output on your system misses a lot of lines! Here is what I expect to happen: ``` sh $ avrdude "-p*" "-c*" >/tmp/avrdude.conf $ avrdude "-p*/r" "-c*/r"...

> Both of them usually provide useful information. I fear you are right, @MCUdude. I am thinking along the lines of recording in `lexer.l` all `#` comments and the location...

@MCUdude Yes, creating a syntax-correct `avrdude.conf` from the internal AVRDUDE representation *after* parsing is but one goal of the developer options. A more important goal is to be able (in...

> multiple inheritance @MCUdude Yes, this is now possible, at the very least by hand. I was thinking that, algorithmically, there is the potential for a chip from a family...

This commit finalises the PR and for the developer options. Now comments in avrdude.conf are associated to the - Space before programmer/part/memory definition - Line before an assignment - Right...

@mcuee Thanks! I removed the sources for the compiler warning bar one: ``` [57/63] Building C object src/CMakeFiles/avrdude.dir/term.c.obj In function 'tokenize', inlined from 'terminal_mode' at C:/work/avr/avrdude_test/avrdude_sr/src/term.c:1301:12: C:/work/avr/avrdude_test/avrdude_sr/src/term.c:1188:15: warning: pointer 'buf'...

Should close Issue #964

However, I was alarmed to see ``` config_gram.y: warning: 28 shift/reduce conflicts [-Wconflicts-sr] ``` in @mcuee's output (something that our cmake configuration hides). Just updated `config_gram.y` to remove the grammar...