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.

Sign up for GitHub

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

Jump to bottom

Optional iostream usage #84

Open
psiha opened this issue Mar 3, 2023 · 5 comments
Open

Optional iostream usage #84

psiha opened this issue Mar 3, 2023 · 5 comments
Labels
enhancement New feature or request

Comments

@psiha
Copy link
Contributor

psiha commented Mar 3, 2023

Somewhat related to #83.

Please provide an build time option to (not) use/provide iostream functionality (eg. ifdef wrapping of std::ostream& operator<<).
@psiha psiha added the enhancement New feature or request label Mar 3, 2023
@jfalcou
Copy link
Owner

jfalcou commented Mar 3, 2023

We pondered the fact to put all operator<< in a io.hpp header and not include it by default.
Sounds enoguh for your use case ?

@psiha
Copy link
Contributor Author

psiha commented Mar 8, 2023

sure - that sounds even better than a configuration macro but more work on your side i suppose - so which ever solution you want 👍

@jfalcou
Copy link
Owner

jfalcou commented Mar 18, 2023 •
edited
Loading

Could you confirm that the issue is operator<< and not the mere include of <iostream> ?

@psiha
Copy link
Contributor Author

psiha commented Mar 20, 2023

both :D

@jfalcou
Copy link
Owner

jfalcou commented Mar 20, 2023

This means our whoel stack shoudl be adapted: kumi & raberu are also affected by this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@jfalcou @psiha