Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
A16-0-1 Use #define for conditional file inclusion?
#3
I too have issue with the rules regarding the preprocessor directives in my line of work. Much of what I do is interfacing higher level algorithmic C++ code with POSIX API system functions, and my wrapper classes are about 90% non-compliant. Frequently running into violations surrounding the concept of "system frameworks" and reusable libraries. If I generate a shared utility library .so then I can pretty much guarantee that not ever class/method in it will be used in the target application.

The OP example is extremely relevant when designing platform portable code for multiple embedded environments.
Reply


Messages In This Thread
RE: A16-0-1 Use #define for conditional file inclusion? - by kent.dorfman766 - 25-08-2022, 02:09 AM

Forum Jump:


Users browsing this thread: 2 Guest(s)