I have been testing out bstring, and it seems to fulfill most of my expectations. One small problem is that there are no function decorations (or def file) for making a DLL version on windows. Is this already available and I missed it?
Thanks,
Greg
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Uhh ... how would you fill in the DLLMain() call? I haven't done this nor thought of how I really would do it. The implementation pretty much follows from the interface, so I am not sure what the value add of making BstrLib into a DLL. Does it make sense for your program to upgrade or modify the way BstrLib works independently from the rest of your program?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Didn't expect to see a reply, that's why my reply is so late! Well in my defense, your reply was late too. :-)
I don't need the DLL version any more, but in answer to your question there are lots of reasons for using a shared library. The reason I use them because I distribute about 35 executables and I like to reduce the footprint. So I follow default policy to use DLLs on windows, but I make an exception for bstrlib!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi,
I have been testing out bstring, and it seems to fulfill most of my expectations. One small problem is that there are no function decorations (or def file) for making a DLL version on windows. Is this already available and I missed it?
Thanks,
Greg
Uhh ... how would you fill in the DLLMain() call? I haven't done this nor thought of how I really would do it. The implementation pretty much follows from the interface, so I am not sure what the value add of making BstrLib into a DLL. Does it make sense for your program to upgrade or modify the way BstrLib works independently from the rest of your program?
Didn't expect to see a reply, that's why my reply is so late! Well in my defense, your reply was late too. :-)
I don't need the DLL version any more, but in answer to your question there are lots of reasons for using a shared library. The reason I use them because I distribute about 35 executables and I like to reduce the footprint. So I follow default policy to use DLLs on windows, but I make an exception for bstrlib!