>I consider a wrapper to be any interface that hides complexity, whether it's object-oriented or just a plain old procedural prg.

I would disagree. A wrapper is something thats wrapps itself around existing code, not just moving existing code, but actually moving existing code and giving it a new interface (for the developers view) to deal with issues like bugs and confusing, which is easier for the next developer to use (maybe yourself).

I would think that simply moving some redunant code into a procedure and calling it many times is not a "wrapper".