config file name too generic?
Opened this issue · 4 comments
I'm currently still using gzstream, but was looking for an updated interface and bxzstr looks pretty good!
However, the config.hpp file could potentially cause ambiguity depending on what the final include path looks like.
Would it be possible to rename as bxzstr_config.hpp (for example), to preclude any such problems (or did I miss something)?
Hi, thanks for the report, I've run in to the same problem with the file being being too generic and agree this makes sense to change. I'll look into it.
Hi, thanks for the report, I've run in to the same problem with the file being being too generic and agree this makes sense to change. I'll look into it.
I have actually made a number of other changes as well (to avoid other include name collisions). Unfortunately they are on another machine and I don't have access to the changeset for the next two weeks (machine is offline). If you want to hang on until then, I can post them for you to inspect/grab/merge as you see fit.
Yes, this would be useful if you can share it. No hurry though.
added to pull-request 28 but not well tested.