Mirror of forum.nim-lang.org

521 :: Defined vs declared

• Araq (orginal) [2014-08-10T13:00:02+02:00] view original

  Bug https://github.com/Araq/Nimrod/issues/1469 is the last one in a series of bugs that results from the fact that Nimrod's defined builtin conflates 2 different things:

  1. Check whether a define is active that comes from a --define (-d) command line / config option.
  2. Check whether some Nimrod symbol is declared.

  This is error prone, we need to distinguish between these two. So we plan to have a``system.defined`` that only does (1) and system.declared that only does (2). The compiler will warn about old usages of defined but this cannot be done reliably, so beware.

---

• Araq (orginal) [2014-08-11T21:28:45+02:00] view original

  This has been implemented. The compiler recognizes lots of "builtin" defines but others need to be explicitly declared via --symbol:mydefine (you can put this into your config file too) otherwise a warning is generated. This way you can easily update your code: When the compiler produces no warning, there is nothing to fix.

---