dll size (topic to discuss)

[Peter A. Volchek]

Hi everyone, Please respond who built the project on OS390 (MVS) What is your the dll size of the release build on this platform (for Xerces 2.1) ? My is ~12Mb that seems too much and becomes the head ache. (Although the IBM's toolkit for os390, based on Xerces 1.6, weighs ~9Mb, so maybe 12 is Ok ?)   --------------------------------------------   Actually I wanted long time ago to raise the question about Xerces toolkit. Not just limited Xerces Lite, but the set of Xerces dlls that will allow to use the xerces functionality required at the moment and will significatnly reduce the memory usage (and time to load dll) Looking at the headers you might see the export directives, like: XMLUTIL_EXPORT XMLPARSER_EXPORT SAX_EXPORT SAX2_EXPORT CDOM_EXPORT PARSERS_EXPORT VALIDATORS_EXPORT   Probably at the initial period of development there were an idea of a separate components ?   Wouldn't it be great to have, for example: xrcs_util.dll xrcs_core.dll xrcs_dom.dll xrcs_parser.dll xrcs_dtdvalidator.dll xrcs_schemavalidator.dll ... xrcs_xalan.dll xrcs_xpath.dll   But, when I tried to separate myself the xerces to different componetns I failed, since the current components layout is not sufficient, and actually these export directives are just fictions. Equally well they may provide a single XERCES_EXPORT directive for all classes, since one may not be able to build a single dll because of the knotty (recursive) dependency between the components.   So, dll grows. Not only on MVS but on other platforms also. New features are added. New features are planned to add. Suppose in one year or two the dll will grow up to 20Mb. How do you think, will the end-consumer be satisfied with this ? Isn't it better to start thinking about it now ?   Regards, Peter A. Volchek