A wrapper pre-processor for implementing domain-specific reusable components

Many of the industry standards for component-based development follow a distributed component model as opposed to a local component model. Using the local component model, this research first defines the component that benefits the development process where the component may be the source code of a module, class, library, function, or code snippet. This research also defines the components' domain as atomic where each domain has a group of closely related components, and each domain has a wrapper (interface) through which users of the atomic domain utilize one or more of its components in the development process. Together these comprise a general model from which has evolved the concept of the Wrapper Pre-Processor - a compiler-side device which aides the implementation of reusable code between the source code and the wrappers after the preprocessor is executed. The component selection is based upon rules programmed into each wrapper's manager as determined by human analysis of past reusable source code in a given application domain.