There appears to be a bug with commenting in prj.conf. If I do this:
There appears to be a bug with commenting in prj.conf. If I do this:
Hi,
Yes, we are aware of this being the case. I guess everything after the equals sign is considered a part of the value, unless you explicitly end the value using a final quotation mark. Another thing that would separate KConfig from what you would eg. expect from C, is that a using spaces between the equals sign can be an issue as well.
But I wouldn't think of any of these as a bug per se - it is how to parser works. It has some limitations but that is typically considered fine. You can eg. add the comment on a different line, and don't need the spaces.
I guess it would be better if the parser looked for this issue, to make the error codes easier to work with. I haven't heard of any plans to fix this.
Regards,
Elfving
Hi,
Yes, we are aware of this being the case. I guess everything after the equals sign is considered a part of the value, unless you explicitly end the value using a final quotation mark. Another thing that would separate KConfig from what you would eg. expect from C, is that a using spaces between the equals sign can be an issue as well.
But I wouldn't think of any of these as a bug per se - it is how to parser works. It has some limitations but that is typically considered fine. You can eg. add the comment on a different line, and don't need the spaces.
I guess it would be better if the parser looked for this issue, to make the error codes easier to work with. I haven't heard of any plans to fix this.
Regards,
Elfving