embitzForum
  • Status New
  • Percent Complete
    50%
  • Ticket Type Feature Request
  • Category
  • Assigned To No-one
  • Operating System All
  • Severity Medium
  • Priority Normal
  • Reported Version 1.21
  • Due in Version Undecided
  • Due Date Undecided
Attached to Project: EmBitz IDE
Opened by Admin (EmBlocks) - 2013-10-19
Last edited by Admin (EmBlocks) - 2013-12-02

Ticket#11 - Smart pre-processor evaluation (Compiler internal & multiple files)

This feature is to make the pre-processor inactive code styling more meaningful. The internal compiler and command line #defines should be used as well as that as starting point the styling file is used to evaluate all #defines from multiple files.

This ticket does not depend on any other tickets.

bobagi (BobAGI)
Friday, 11 April 2014, 12:09 GMT
To clarify:
Consider a project that uses a single or a limited number of header files, which summarize all standard headers needed and also the defines for the project such as MCU pin utilization etc.
In such a project the individual c files contain only one or two #include directives pointing at these summary headers.
This is very convenient when a project contains more than a single or couple of source files.
BUT
in this situation the syntax highlighter is completely wrong about which blocks of code are actually used. EVERYTHING is colored as inactive!

One proposal that would enhance the functionality is to let the parsing of the files to evaluate preprocessor exclusions scan at least one level of header files too.
In order to limit further the scope (to speed up scanning?) one could limit the scanning to only those header files that have been explicitly added to the project so they are listed in the project source list.

In any case it would help immensely with project development in multi-target situations when this kind of define system is commonly used.

Loading...