General Guidelines For C++ library development
-
Hi there, I have a library that I want to publicy. It gives different facilities to C++ developers wanting to develop server application. Are there general guidelines that can be useful ?
Easy Profiler : Now open source ! http://www.codeproject.com/KB/cpp/easyprofiler.aspx
-
Hi there, I have a library that I want to publicy. It gives different facilities to C++ developers wanting to develop server application. Are there general guidelines that can be useful ?
Easy Profiler : Now open source ! http://www.codeproject.com/KB/cpp/easyprofiler.aspx
About making the library yes, but ... it is a question you'd had to investigate BEFORE deploying the library ... The only thing they can tell you right now is that you have to rewrite it based on a different coding standard on environmental assumption ! About public it, well... You have to document its functionality and its usage, either in informal way (describe the design and the way it should be used to accomplish certain tasks - this part should be readable like a book) and in formal way (alphabetical order of classes, functions, parameters, input output, processing, side effects, little testing samples etc. You can try to have a clue about this can be done by looking existing library's documentation, like boost[^] (the link points just to an example), or MSDN[^] (just another sample) etc.
2 bugs found. > recompile ... 65534 bugs found. :doh:
-
Hi there, I have a library that I want to publicy. It gives different facilities to C++ developers wanting to develop server application. Are there general guidelines that can be useful ?
Easy Profiler : Now open source ! http://www.codeproject.com/KB/cpp/easyprofiler.aspx
Walkthrough: Creating and Using a Static Library http://msdn.microsoft.com/en-us/library/ms235627(VS.80).aspx Walkthrough: Creating and Using a Dynamic Link Library http://msdn.microsoft.com/en-us/library/ms235636(VS.80).aspx