Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Logger improvement #56

Open
carmenfan opened this issue Nov 20, 2015 · 0 comments
Open

Logger improvement #56

carmenfan opened this issue Nov 20, 2015 · 0 comments

Comments

@carmenfan
Copy link
Member

As far as I understand it, boost_log_trivial is inefficient (something to do with creating a new sink every time) and we should look into using the standard boost logger.

Also, instead of using a macro to directly map repoError repoTrace etc. to BOOST_LOG_TRIVIAL, we should have our own LoggerStream that should do the same thing to decouple the relationship, This will allow programs built on top of the bouncer (i.e. gui) can use the same instance of logger without using a special function (repoLog and repoLogError atm). This is probably naturally achieved when we move onto the standard boost logger.

@carmenfan carmenfan modified the milestone: 3drepobouncer 1.0b Dec 16, 2015
@carmenfan carmenfan modified the milestones: 3drepobouncer 1.0b, Next Release Mar 21, 2016
carmenfan added a commit that referenced this issue Mar 31, 2016
carmenfan added a commit that referenced this issue Apr 4, 2016
@carmenfan carmenfan removed this from the Next Release milestone Feb 28, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant