Differences between version 2 and predecessor to the previous major change of perlvms(1).
Other diffs: Previous Revision, Previous Author, or view the Annotated Edit History
| Newer page: | version 2 | Last edited on Tuesday, June 4, 2002 12:22:40 am | by perry | Revert |
| Older page: | version 1 | Last edited on Tuesday, June 4, 2002 12:22:40 am | by perry | Revert |
@@ -58,15 +58,15 @@
delete this image.
Most of the complete Perl resides in the shareable image
-''PerlShr.Exe'', which provides a core to which the Perl
+''!
PerlShr.Exe'', which provides a core to which the Perl
executable image and all Perl extensions are linked. You
should place this image in ''Sys$Share'', or define the
-logical name ''PerlShr'' to translate to the full file
+logical name ''!
PerlShr'' to translate to the full file
specification of this image. It should be world readable.
(Remember that if a user has execute only access to
-''PerlShr'', VMS will treat it as if it
+''!
PerlShr'', VMS will treat it as if it
were a privileged shareable image, and will therefore
require all downstream shareable images to be INSTALLed,
etc.)
@@ -96,12 +96,12 @@
The portion of the extension provided by the
XS code may be connected to the rest of Perl
in either of two ways. In the __static__ configuration,
the object code for the extension is linked directly into
-''PerlShr.Exe'', and is initialized whenever Perl is
+''!
PerlShr.Exe'', and is initialized whenever Perl is
invoked. In the __dynamic__ configuration, the
extension's machine code is placed into a separate shareable
-image, which is mapped by Perl's DynaLoader when the
+image, which is mapped by Perl's !
DynaLoader when the
extension is used or required in your
script. This allows you to maintain the extension as a
separate entity, at the cost of keeping track of the
additional shareable image. Most extensions can be set up as
@@ -114,26 +114,26 @@
portion of the extension's name following the last
::), containing the XS code,
''Extshortname.pm'', the Perl library module for the
extension, and ''Makefile.PL'', a Perl script which uses
-the MakeMaker library modules supplied with Perl to
+the !
MakeMaker library modules supplied with Perl to
generate a ''Descrip.MMS'' file for the
extension.
__Installing static extensions__
Since static extensions are incorporated directly into
-''PerlShr.Exe'', you'll have to rebuild Perl to
+''!
PerlShr.Exe'', you'll have to rebuild Perl to
incorporate a new extension. You should edit the main
''Descrip.MMS'' or ''Makefile'' you use to build Perl,
adding the extension's name to the ext macro, and
the extension's object file to the extobj macro.
You'll also need to build the extension's object file,
either by adding dependencies to the main
''Descrip.MMS'', or using a separate ''Descrip.MMS''
-for the extension. Then, rebuild ''PerlShr.Exe'' to
+for the extension. Then, rebuild ''!
PerlShr.Exe'' to
incorporate the new code.
Finally, you'll need to copy the extension's Perl library
@@ -183,17 +183,17 @@
the installed Perl directory tree (where ''Arch'' is
''VMS_VAX'' or
''VMS_AXP'' , and ''Extname'' is the
name of the extension, with each :: translated to
-.). (See the MakeMaker documentation for more
+.). (See the !
MakeMaker documentation for more
details on installation options for extensions.) However, it
can be manually placed in any of several locations: - the
''[[.Lib.Auto.Arch$PVersExtname]'' subdirectory of one of
the directories in @INC (where ''PVers'' is the
version of Perl you're using, as supplied in $],
with '.' converted to '_'), or - one of the directories in
@INC, or - a directory which the extensions Perl
-library module passes to the DynaLoader when asking it to
+library module passes to the !
DynaLoader when asking it to
map the shareable image, or - ''Sys$Share'' or
''Sys$Library''. If the shareable image isn't in any of
these places, you'll need to define a logical name
''Extshortname'', where ''Extshortname'' is the
