|
Extending and Embedding Perl Tim Jenness and Simon Cozens 2002 | 384 pages ISBN: 1930110820 |
|||
 |
$22.50 | PDF ebook | |
|
$44.95 | Softbound print book | |
Preface
Perl is a wonderful language. We, along with at least a million other programmers, love it dearly. It’s great for all kinds of applications: text processing, network programming, system administration, and much more. But there are times when we need to go beyond the core of the language and do something not provided by Perl.
Sometimes we do this without noticing it: several modules that ship with Perl call out to C routines to get their work done, as do some of the most commonly used CPAN modules. Other times, we do it deliberately: the various modules for building graphical applications in Perl almost all, directly or indirectly, use external C libraries. Either way, writing extensions to Perl has historically been a bit of a black art. We don’t believe this situation is fair, so we’ve written this book to attempt to demystify the process of relating Perl and C.
That’s not to say we’re fed up with writing modules in Perl. Both of us write many of our modules in Perl, and although sometimes it might be easier to interface to C, we’ve decided to stick with Perl. In fact, writing a module in Perl has a number of advantages over using other languages:
- It is far easier to write portable cross-platform code in Perl than in C. One of the successes of Perl has been its support of varied operating systems. It is unlikely that a module written in C could be as portable as a Perl version without much more effort on the part of the programmer, precisely because Perl strives to hide the complexities of differences between underlying operating systems from the programmer.
- Some problems do not need the speed gain that comes from using a compiled language or the added complexity of interfacing to another language. For many programmers who are proficient in Perl (and/or Java), writing a Perl module is much more efficient (in terms of programming effort) than writing the equivalent in C.
People program in Perl for a reason, and this fact should not be forgotten when it comes to deciding whether to use Perl for an extension module. These issues were addressed in the development of the standard File::Temp module (part of Perl 5.6.1). This module provides a standard interface for creating temporary files from Perl. The original intention was that this module would be written in C, but it quickly became apparent that a Perl implementation would be easier because of portability problems (it was to be a standard module, so it would have to work on all platforms supported by Perl); in addition, speed would not be an issue unless thousands of temporary files were required.
Having addressed why not to use a language other than Perl, we must now present two important reasons why another language is sometimes required:
- Speed—In some cases, Perl is simply too slow for a particular program. In this case, the choice is either to change the algorithm or to use a faster programming language. The Perl Data Language was created specifically to address the case of processing N-dimensional arrays, but there are times when another language is required. Similarly, Perl is definitely too slow for some tasks (for instance, the graphics manipulation functions provided by Imager and GD).
- Functionality—Many useful libraries have been written in other languages (especially C, and for numerical applications, Fortran). If new functionality is required that is present in an external library, then it is usually far better to provide a Perl interface to the library than to recode the library in Perl. For instance, the XML::Parser module provides a reasonably direct mapping onto the underlying functions of the expat library. Functionality is particularly an issue for things that simply can’t be written in Perl, such as interfaces to certain system libraries (for instance, the Macintosh Carbon library) or to particular pieces of hardware.
As well as extending Perl by writing modules in C, sometimes it’s advantageous to go the other way around: to add the flexibility of a Perl interpreter to an existing C program. Like extending, this process has a fearsome reputation, and so we provide two chapters on the topic. Chapter 8 introduces embedding Perl, and chapter 9 includes a full working example that explains Perl embedding.
We also realize that people want to know what’s really going on under the hood, so we conclude our study of the interaction between C and Perl by examining the C sources of the perl interpreter itself, together with details of how to get involved in becoming a developer maintaining perl. Finally, we look ahead to Perl 6 and the Parrot project.
DESCRIPTION
Extending and Embedding Perl explains how to expand the functionality and usefulness of the Perl programming language and how to use Perl from C programs. It begins simply but also covers complex issues using real code examples from the Perl source. The book discusses how to write interfaces to C libraries (as well as C++ and Fortran libraries). It shows you how to implement Perl callbacks for C libraries, how to pass Perl hashes and arrays between Perl and C, and how to use the Perl Data Language infrastructure to improve the speed of array operations.
Additionally, the book peers under the hood to see how the Perl programming language really works by looking at the interpreter. The make-up of Perl variables is discussed along with details on how a Perl program is parsed and converted to executable code.
What's Inside:
- C For The Perl Programmer
- Basic and Advanced XS
- Embedding Perl in C Programs
- Perl Internals
- An API reference for the internal C interface to Perl
- A reference on the typemap system
- Embedding Perl into the mutt mail reader
ABOUT THE AUTHORS...
A Perl developer for 7 years, Tim Jenness has ten modules on CPAN including two that are distributed as part of the core Perl distribution (File::Temp and Pod::LateX).
Simon Cozens the author of Beginning Perl, was the release manager for the first four releases of the Perl 6 runtime engine, Parrot.