Hi, The Keil MDK shows an error when I open a example project from nrfSDK. but there is no error when compile.
Could someone please clarify. Thank you .
Hi, The Keil MDK shows an error when I open a example project from nrfSDK. but there is no error when compile.
Could someone please clarify. Thank you .
Hi,
I have the same thing at my computer.
It seems that this is an issue with the code-completion feature in Keil. The code-completion option does some parsing of the file and it's included headers, and seem to miss this declaration somehow.
As you point out, there's no compiler-error, so it's safe to ignore.
Best regards Håkon
Hi,
I have the same thing at my computer.
It seems that this is an issue with the code-completion feature in Keil. The code-completion option does some parsing of the file and it's included headers, and seem to miss this declaration somehow.
As you point out, there's no compiler-error, so it's safe to ignore.
Best regards Håkon
I've also gotten the same error since I ugpraded Keil a little while ago.
None of my code is anymore broken than normal, so also confirm it's more of a cosmetic issue ;)
-m
I agree. I was facing the same issue a few days ago until i realized that is was more for cosmetic reasons than syntactical.
Three years later and this problem is still there. :-(
I actually talked to Keil/ARM about this at a embedded conference. This is a restriction in their autocompletion tool, where it does not properly parse function implementations in header files. It shall not have any effect on your compilation, but it is annoying to see from a user-perspective.
That is true. However, a professor of user interface design theory would be screaming about this kind of thing. :-) A modern IDE should be presenting the developer with a easier workload and an accurate representation of the current state of the code.
In some ways this reminds me of not fixing compile warnings. Sure, your code may work, but there may be a real problem hiding in that stream of warnings. If you can't trust your IDE to accurately display if a problem is real or not, potentially you'll miss actual problems in your code that the compiler is trying to warn you about.