You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was looking over an old C++ implementation and saw how I'd broken the log call into three parts: the area/component, a tag or bitset, and the log parameters. This makes it straightforward to have manageable tag spaces for multiple components that are relatively fast and don't use BigInt (bitsets in C++). For what was a fairly complex application there were less than 50 global tags, but each area/component could have up to 128 private tags. I don't need this this personally, but would welcome. There was also an interface to limit logging by level, which is, again, for me not an issue, but could be for automated testing.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
I was looking over an old C++ implementation and saw how I'd broken the log call into three parts: the area/component, a tag or bitset, and the log parameters. This makes it straightforward to have manageable tag spaces for multiple components that are relatively fast and don't use BigInt (bitsets in C++). For what was a fairly complex application there were less than 50 global tags, but each area/component could have up to 128 private tags. I don't need this this personally, but would welcome. There was also an interface to limit logging by level, which is, again, for me not an issue, but could be for automated testing.
Beta Was this translation helpful? Give feedback.
All reactions