Putting a comment after an int in prj.conf causes an error

[Calvin T]

There appears to be a bug with commenting in prj.conf. If I do this:

# This is the appearance of the device from the BLE SIG Assigned Numbers List (384 is general remote co

CONFIG_BT_DEVICE_APPEARANCE=384

...it works fine. If I do this:

CONFIG_BT_DEVICE_APPEARANCE=384               # This is the appearance of the device from the BLE SIG Assigned Numbers List (384 is general remote co

...it does not. The problem appears to be comments that follow the assignment on the same line. This is not a problem when the config is boolean or a string.

CONFIG_BT_DIS_FW_REV_STR="FD-98562-01.0000000000"   # This is the SmartPac Firmware part number for the particular application. It's in the formate o

...works fine, as an example.

Is Team Nordic aware of the bug, and are there any plans to fix it?

[Seraphina]

To make the error codes easier to work with, I suppose it would be preferable if the parser searched for this problem. As far as I know, there are no plans to address this. Baseball Bros IO

[plussouvenir]

I just encountered a similar problem when specifying parameters in the 'prj.conf' file for an embedded project. I discovered that misplaced comments might lead to irritating issues! It was a huge relief when I realized that even little syntax errors may derail everything. Thank you for bringing this to our attention; it's something that everyone who works with Nordic's tools should be aware of block blast! Your insights are always helpful and contribute to a smoother growth path.