Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!thunder.mcrcim.mcgill.edu!snorkelwacker.mit.edu!usc!cs.utexas.edu!samsung!munnari.oz.au!metro!extro!objtch From: objtch@extro.ucc.su.OZ.AU (Peter Goodall) Newsgroups: comp.object Subject: Re: "Wrappers" and "Container Objects" Keywords: wrappers, container objects Message-ID: Date: 27 Jun 91 07:35:26 GMT References: <1991Jun26.165456.17545@m.cs.uiuc.edu> <1991Jun26.192616.24163@milton.u.washington.edu> Sender: news@metro.ucc.su.OZ.AU Organization: Sydney University Computing Service, Sydney, NSW, Australia Lines: 13 Nntp-Posting-Host: extro.ucc.su.oz.au I have most often seen the term "Wrapper" used in the the context of creating an Object Oriented Smalltalk class to contain some 'procedural' code from a foreign Application Progaramming Interface. For example I recently built what I would call a Smalltalk "wrapper" for Wang's Open Image API. So I can use the C-style API calls via a synthesised Smalltalk subclass of Window. This lets me work in Smalltalk's normal high-level way without seeing any nasty C. -- Peter Goodall - Smalltalk Systems Consultant - objtch@extro.ucc.su.oz.au ObjecTech Pty. Ltd. - Software Tools, Training, and Advice 162 Burns Bay Rd, LANE COVE, NSW, AUSTRALIA. - Phone/Fax: +61 2 418-7433