3 ms·
Actually, I'm not sure. If we're referring to the C pre-processor here, can't we always just run it through before symbolizing? I guess that without the right
by KirinDave 9y ago
Actually, I'm not sure. If we're referring to the C pre-processor here, can't we always just run it through before symbolizing?
I guess that without the right environment ifdef stuff falls out, but I dunno what to tell you there other than making builds contingent on the environment is a sketchy practice.
- joshuamorton 9y agoSo, say I have this: #include a.h #include b.h #include c.h MACRO(varname) welp.
- KirinDave 9y agoSince the include chain has to terminate, can't we just run the pre-processor over every file before we index it? Seems, um, like a pretty reasonable idea to me if you care about C-style macros (I sure don't.)
- majewsky 9y agoIt may be sketchy, but you may not have a choice. If you have a Qt application (written in C++) which needs to use a platform-specific API to do some magic stuff with a window, there's a method on the window to get the handle that the platform's GUI library offers. Of course that's going to be dependent on the environment because each environment has an entirely different GUI library (e.g. Cocoa only exists on macOS, not on Windows or Linux or Android).