| If it's code size ... The major issue (IMHO) is to keep the working set down (in a MS environment), so the app does not have to take page faults.
That is certainly true and a nice way of summing up my advice regarding wrapping up the required use in his own API so that the exposed set of Crypto++ calls (and requisite code) is minimized and controlled by the linker.
| What OS ... The trend for MS desktop applications is to get away from DLLs due to DLL hell. Memory is basically no longer an issue. I cannot speak intelligently about Symbian, Palm, Linux, and WinCE (I do have some experience with CE). Again, I have read it (re: a reference), but I can't find it. Richter talks about the Link/Loader and DLLs and altered search paths in his book "Programming Applications for Windows" (ISBN 1-57231-996-8), chapters 19 or 20.
That should now be mitigated a lot by Microsoft's new DLL packaging technique with .NET (and works on older systems), but like you have only read about it.
Regardless, this isn't a desktop app, so size is often still a major consideration: a big DLL can make for unacceptable download size when we are talking about embedded architectures, regardless of target OS.
michael
