[SERVER-7233] LOG macro can leak into client code. Created: 02/Oct/12 Updated: 10/Dec/14 Resolved: 22/Jul/14 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Internal Code |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Minor - P4 |
| Reporter: | Andy Schwerin | Assignee: | Unassigned |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Operating System: | ALL | ||||||||||||||||
| Participants: | |||||||||||||||||
| Description |
|
The LOG() macro should either have a MONGO_ prefix or not be included in any header included by client code, to avoid polluting the client namespace. |
| Comments |
| Comment by Ben Becker [ 02/Oct/12 ] |
|
Current proposal is to split the definition of LOG and MONGO_LOG into separate header files. No header file should include the LOG definition; instead it should include the file that defines MONGO_LOG(). |