• State Not Answered
  • Locked Locked
  • Replies 14 replies
  • Subscribers 21 subscribers
  • Views 2072 views
  • Users 0 members are here
2025 survey

We are running a survey to help us improve the experience for all of our members. If you see the survey appear, please take the time to tell us about your experience if you can.

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

#message

Martin Green

Hi,
Does anyone here ever use #message in other compilers?

It is a useful tool for making sure that code with many #ifdef compiles the way you want without adding to the number of warnings.


thanks,
Martin

Parents Reply Children
  • 0 in reply to Martin Green

    "If you want to use the ide, then I think what you suggest may be complicated"

    Although I haven't actually tried it, I think it should be quite easy using the Custom Translation facility...?

  • 0 in reply to Martin Green

    "...that sounds like you are not using MicroVision2."

    Ah yes, you are correct. Given the number of different processors and toolchains I deal with, I don't use anybody's IDE except for simulation/debug. Just like I design firmware to be as processor-independent as I possibly can, I use a build environment that is as toolchain-independent as I can possibly get it. I can't afford to be hamstrung dealing with vendors' IDE idiosyncrasies for editing, building, etc.

    "If you want to use the ide..."

    Now why would I want to do that? ;-)

    "...then I think what you suggest may be complicated (could be wrong on this though)"

    I think you'd be right (but I could be wrong).

  • 0 in reply to Dan Henry

    I see your logic.
    I was given, a month to develop lots of code, and some sample code written in this environment that did some of the things I wanted.

    That made it easy for me to decide; use the sample code and the ide. Now I am fine tuning.

  • 0 in reply to Dan Henry

    I said, "I don't use anybody's IDE..."

    I don't mean to imply that Keil's IDE is bad, so don't get me wrong. Keil's IDE is nice as far as IDEs are concerned.

    Now if all vendors plugged into a common flexible IDE like Eclipse, I might start using an IDE.

  • 0 in reply to Dan Henry

    To my knowledge, #warning is not part of Standard C either.

    Your knowledge is apparently correct. At least from skimming the n869 draft for ISO C99, I don't see #warning mentioned. I was under the delusion it had been added for C99. But apparently not, and #warning is still just a non-standard extension (common or not).