Opened 14 years ago
Closed 14 years ago
#1881 closed Bugs (duplicate)
max() & min() macros are leaking from <windows.h> into entire project
Reported by: | Denis Nesterov | Owned by: | Anthony Williams |
---|---|---|---|
Milestone: | Boost 1.36.0 | Component: | thread |
Version: | Boost 1.35.0 | Severity: | Problem |
Keywords: | min max macros | Cc: |
Description
Macros max() & min() are leaking out of <Windows.h> through boost/thread library, ruining every language construction with words "max" or "min". My solution was to define NOMINMAX before including every boost header. Problems began after upgrading boost from 1.34 to 1.35.
Attachments (2)
Change History (4)
comment:1 by , 14 years ago
comment:2 by , 14 years ago
Resolution: | → duplicate |
---|---|
Status: | new → closed |
This is a duplicate of issue #1825
by , 7 years ago
Attachment: | ExternalDisplay-1.zip added |
---|
by , 7 years ago
Attachment: | ExternalDisplay-1.2.zip added |
---|
Note:
See TracTickets
for help on using tickets.
Futhermore, windows macros "near" and "far" are also active with boost. It's devastating :-)