Example #3 README
This is an example of how to include a statically linked extension
into our proggie, with automatic bootstrap of the extension from
within C space - so that Perl space user scripts don't have to
explicitly `use' the extension, which they'd always have to otherwise,
as long as they'd be intended to run in our custom embedded interpreter.
This particular version of the example was intended to try if
MULTIPLICITY works with this perl from the system-wide build.
In my case, the answer was NO.
Later, I have decided that MULTIPLICITY was not what I was after
- the later examples use threads.
References & credits:
- `man perlembed`
- `man perlxstut`
- `man perlxs`
- `man perlguts`
- "Advanced Perl Programming", "Programming Perl", "Perl in a Nutshell",
"Perl Cookbook" - all four from O'Reilly & Associates
- the sources of Perl 5.005_03 and Perl 5.6.1, in particular ext/Thread/Thread.c
(Damn. 5.8.0 is out just now - gotta take a look.)
- `man gcc`
- USENET newsgroups - several hints on how to compile Perl using a C++
compiler, what to do about -DBOOL=char, how to avoid the assert redefinition