perlmeditation liz Perl is by many considered to be a glue language. Glue with an external library, for instance. Which then becomes one or more modules on the Perl side of things. <P> Whenever you start development of such a (set of) module(s), you need to make a lot of choices. And some of them are very basic. <P> The most basic one, I think, whether the modules that you develop will be Perl-centric or external library-centric. The latter will (probably) give you complete control of all of the functionality of the library (which you may or may not be interested in). The former will give nice extra functionality in Perl. But it may be suffering from the "thick rubber glove" syndrome, i.e. you don't have a feeling anymore for what in fact is happening behind the scenes, and you may not have all the functionality of the external library at your disposal. <P> Personally, I would develop a Perl-centric interface. I have two reasons for that: <OL> <LI>It is what you're used to when programming Perl. <LI>If it is a good interface, it might be transferrable to other external libraries. </OL> <P> I was wondering whether the Perl Monks have anything to say about these choices, and why one should do it one way or the other. <P> Liz