Config file: Allow inline comments

[akira25]

I've come across a recurring issue with the configuration file, which appears to not support inline comments.

For instance, the following works as expected:

# AOIC-Soundcard as reported by arecord -l  
ADEVICE  plughw:3,0

However, adding a comment on the same line causes an error that’s a bit hard to trace:

ADEVICE  plughw:3,0        # AOIC-Soundcard as reported by arecord -l

Which results in:

Dire Wolf version 1.7
Includes optional support for:  gpsd hamlib cm108-ptt

Reading config file aioc.conf
Audio input device for receive: plughw:3,0  (channel 0)
Audio out device for transmit: #  (channel 0)
ALSA lib pcm.c:2722:(snd_pcm_open_noupdate) Unknown PCM #
Could not open audio device # for output
No such file or directory
Pointless to continue without audio device.

It’s a rather subtle issue, and it took me a while to realise that the inline comment was the cause.

It would be fantastic if support for inline comments could be added, or if the parser could at least ignore them more gracefully. This would make the config files a bit more forgiving and user-friendly.

Thanks a lot for your great work on this project!

[wb2osz]

Thanks for the suggestion.
The problem is that the # character can appear in some configuration items.
For example it could be in a beacon comment or symbol type filter.
Ignoring # and everything after it would break existing functionality.