tis 2010-08-24 klockan 19:15 -0600 skrev Alex Rousskov: > The current header sequence (somewhere) violates the squid-then-sys rule > and causes the problem. A header sequence that follows the > squid-then-sys rule will not cause the problem. I suspect such sequence > does not exist (beyond one file scope) because some Squid headers have > to include system headers.
And I say the opposite. The sequence that can fork is sys headers first then squid headers with #undef. The keywords are used both in the squid header and in squid code. squid heders first then sys headers renders the squid code using these members directly broken. Regards Henrik
