• State Not Answered
  • Locked Locked
  • Replies 15 replies
  • Subscribers 22 subscribers
  • Views 9657 views
  • Users 0 members are here
Options
Related
How was your experience today?
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

..\display.h(72): warning: #231-D: declaration is not visible outside of function

Bruce Partridge

..\display.h(72): warning: #231-D: declaration is not visible outside of function

I got message when I included a header file containing this line:

void DISPLAY_string_date_time(const struct tm * tim, DISPLAY_MSG * p_message);

I found the problem - I hadn't included <time.h> in the two cases that caused the warning.

After a lot of searching for what this warning means, I can't find any explanation.

Can anyone translate what the compiler is saying?

Parents
  • 0 in reply to Bruce Partridge

    Not without seeing your actual source code, of course.

    But I very much suspect that it is as I suggested: your initial error(s) due to the missing header have thrown the compiler so far out-of-sync with your source text that it is giving apparently meaningless messages.

    Sometimes it can get so grossly out-of-sync that it will actually crash!

    If you really want to pursue it, you need to look at the point of the very first error and ask yourself what the compiler is assuming was there - having rejected what you actually wrote as invalid, and so on...

    But, as I said, it is pointless - just fix the original error, and that will naturally fix all the consequent errors!

Reply
  • 0 in reply to Bruce Partridge

    Not without seeing your actual source code, of course.

    But I very much suspect that it is as I suggested: your initial error(s) due to the missing header have thrown the compiler so far out-of-sync with your source text that it is giving apparently meaningless messages.

    Sometimes it can get so grossly out-of-sync that it will actually crash!

    If you really want to pursue it, you need to look at the point of the very first error and ask yourself what the compiler is assuming was there - having rejected what you actually wrote as invalid, and so on...

    But, as I said, it is pointless - just fix the original error, and that will naturally fix all the consequent errors!

Children