Hi there, I find it a bit weird why the guid needs to be built. I think the designer did it because of the sha1 lib. But how about having guid lib header only when you want everything but the create_v5 part? I think that would make sense. I wouldn't mind reorganizing the code. Christian
"Christian Henning"
Hi there, I find it a bit weird why the guid needs to be built. I think the designer did it because of the sha1 lib. But how about having guid lib header only when you want everything but the create_v5 part?
I think that would make sense. I wouldn't mind reorganizing the code.
Christian
Hi, I have been considering making the guid library header only. You are the second to suggest it. I could make the sha1 library part header only as well, so that the whole library (including create_v5) would be header only. I was waiting until the review to determine if this is the route I should take. As I see it, the rationale for changing to a header only library would be similar to the boost timer library rationale (for it being a header only library). Andy.
Andy wrote:
"Christian Henning"
wrote in news:949801310702221230xf590063r3d22ee1f54e1ecbd@mail.gmail.com: Hi there, I find it a bit weird why the guid needs to be built. I think the designer did it because of the sha1 lib. But how about having guid lib header only when you want everything but the create_v5 part?
I think that would make sense. I wouldn't mind reorganizing the code.
Christian
Hi,
I have been considering making the guid library header only. You are the second to suggest it. I could make the sha1 library part header only as well, so that the whole library (including create_v5) would be header only. I was waiting until the review to determine if this is the route I should take.
+1 for header-only. I've been thinking about that since the first time I heard about the library. / Johan
participants (3)
-
Andy
-
Christian Henning
-
Johan Nilsson