1 If you read this file _as_is_, just ignore the equal signs on the left.
2 This file is written in the POD format (see [.POD]PERLPOD.POD;1) which is
3 specially designed to be readable as is.
7 README.vms - Configuring, building, testing, and installing perl on VMS
11 To configure, build, test, and install perl on VMS:
18 mmk may be used in place of mms in the last three steps.
22 =head2 Important safety tip
24 The build and install procedures have changed significantly from the 5.004
25 releases! Make sure you read the "Configuring the Perl Build", "Building
26 Perl", and "Installing Perl" sections of this document before you build or
27 install. Also please note other changes in the current release by having
28 a look at L<perldelta/VMS>.
30 Also note that, as of Perl version 5.005 and later, an ANSI C compliant
31 compiler is required to build Perl. VAX C is *not* ANSI compliant, as it
32 died a natural death some time before the standard was set. Therefore
33 VAX C will not compile Perl 5.005 or later. We are sorry about that.
35 If you are stuck without Compaq (formerly DEC) C consider trying Gnu C
36 instead, though there have been no recent reports of builds using Gnu C.
37 There is minimal support for Compaq C++ but this support is not complete;
38 if you get it working please write to the vmsperl list (for info see
42 =head2 Introduction to Perl on VMS
44 The VMS port of Perl is as functionally complete as any other Perl port
45 (and as complete as the ports on some Unix systems). The Perl binaries
46 provide all the Perl system calls that are either available under VMS or
47 reasonably emulated. There are some incompatibilities in process handling
48 (e.g. the fork/exec model for creating subprocesses doesn't do what you
49 might expect under Unix), mainly because VMS and Unix handle processes and
50 sub-processes very differently.
52 There are still some unimplemented system functions, and of course we
53 could use modules implementing useful VMS system services, so if you'd like
54 to lend a hand we'd love to have you. Join the Perl Porting Team Now!
56 The current sources and build procedures have been tested on a VAX using
57 DEC C, and on an AXP using DEC C. If you run into problems with
58 other compilers, please let us know. (Note: DEC C was renamed to Compaq C
61 There are issues with various versions of DEC C, so if you're not running a
62 relatively modern version, check the "DEC C issues" section later on in this
65 =head2 Other required software for Compiling Perl on VMS
67 In addition to VMS and DCL you will need two things:
73 DEC (now Compaq) C or gcc for VMS (AXP or VAX).
77 DEC's MMS (v2.6 or later), or MadGoat's free MMS
78 analog MMK (available from ftp.madgoat.com/madgoat) both work
79 just fine. Gnu Make might work, but it's been so long since
80 anyone's tested it that we're not sure. MMK is free though, so
81 go ahead and use that.
85 =head2 Additional software that is optional for Perl on VMS
87 You may also want to have on hand:
91 =item 1 GUNZIP/GZIP.EXE for VMS
93 A de-compressor for *.gz and *.tgz files available from a number
94 of web/ftp sites and is distributed on the OpenVMS Freeware CD-ROM
97 http://www.fsf.org/order/ftp.html
98 http://www.openvms.compaq.com/freeware/
99 http://www.crinoid.com/utils/
103 For reading and writing unix tape archives (*.tar files). Vmstar is also
104 available from a number of web/ftp sites and is distributed on the OpenVMS
105 Freeware CD-ROM from Compaq.
108 http://www.openvms.compaq.com/freeware/
110 =item 3 UNZIP.EXE for VMS
112 A combination decompressor and archive reader/writer for *.zip files.
113 Unzip is available from a number of web/ftp sites.
115 http://www.info-zip.org/UnZip.html
116 http://www.openvms.compaq.com/freeware/
117 ftp://ftp.openvms.compaq.com/
118 ftp://ftp.madgoat.com/madgoat/
119 ftp://ftp.process.com/vms-freeware/
123 Most is an optional pager that is convenient to use with perldoc (unlike
124 TYPE/PAGE, MOST can go forward and backwards in a document and supports
125 regular expression searching). Most builds with the slang
126 library on VMS. Most and slang are available from:
128 ftp://space.mit.edu/pub/davis/
129 ftp://ftp.process.com/vms-freeware/narnia/
131 =item 5 GNU PATCH and DIFFUTILS for VMS
133 Patches to Perl are usually distributed as GNU unified or contextual diffs.
134 Such patches are created by the GNU diff program (part of the diffutils
135 distribution) and applied with GNU patch. VMS ports of these utilities are
138 http://www.crinoid.com/utils/
139 http://www.openvms.compaq.com/freeware/
143 Please note that UNZIP and GUNZIP are not the same thing (they work with
144 different formats). Many of the useful files from CPAN (the Comprehensive
145 Perl Archive Network) are in *.tar.gz or *.tgz format (this includes copies
146 of the source code for perl as well as modules and scripts that you may
147 wish to add later) hence you probably want to have GUNZIP.EXE and
148 VMSTAR.EXE on your VMS machine.
150 If you want to include socket support, you'll need a TCP/IP stack and either
151 DEC C, or socket libraries. See the "Socket Support (optional)" topic
154 =head1 Configuring the Perl build
156 To configure perl (a necessary first step), issue the command
160 from the top of an unpacked perl source directory. You will be asked a
161 series of questions, and the answers to them (along with the capabilities
162 of your C compiler and network stack) will determine how perl is custom
163 built for your machine.
165 If you have multiple C compilers installed, you'll have your choice of
166 which one to use. Various older versions of DEC C had some caveats, so if
167 you're using a version older than 5.2, check the "DEC C Issues" section.
169 If you have any symbols or logical names in your environment that may
170 interfere with the build or regression testing of perl then configure.com
171 will try to warn you about them. If a logical name is causing
172 you trouble but is in an LNM table that you do not have write access to
173 then try defining your own to a harmless equivalence string in a table
174 such that it is resolved before the other (e.g. if TMP is defined in the
175 SYSTEM table then try DEFINE TMP "NL:" or somesuch in your process table)
176 otherwise simply deassign the dangerous logical names. The potentially
177 troublesome logicals and symbols are:
186 As a handy shortcut, the command:
190 (note the quotation marks and case) will choose reasonable defaults
191 automatically (it takes DEC C over Gnu C, DEC C sockets over SOCKETSHR
192 sockets, and either over no sockets). Some options can be given
193 explicitly on the command line; the following example specifies a
194 non-default location for where Perl will be installed:
196 @ Configure "-d" "-Dprefix=dka100:[utils.perl5.]"
198 Note that the installation location would be by default where you unpacked
199 the source with a "_ROOT." appended. For example if you unpacked the perl
202 DKA200:[PERL-5_10_2...]
204 Then the PERL_SETUP.COM that gets written out by CONFIGURE.COM will
205 try to DEFINE your installation PERL_ROOT to be:
207 DKA200:[PERL-5_10_2_ROOT.]
209 More help with configure.com is available from:
213 See the "Changing compile-time options (optional)" section below to learn
214 even more details about how to influence the outcome of the important
215 configuration step. If you find yourself reconfiguring and rebuilding
216 then be sure to also follow the advice in the "Cleaning up and starting
217 fresh (optional)" and the checklist of items in the "CAVEATS" sections
220 =head2 Changing compile-time options (optional) for Perl on VMS
222 Most of the user definable features of Perl are enabled or disabled in
223 configure.com, which processes the hints file config_h.SH. There is
224 code in there to Do The Right Thing, but that may end up being the
225 wrong thing for you. Make sure you understand what you are doing since
226 inappropriate changes to configure.com or config_h.SH can render perl
227 unbuildable; odds are that there's nothing in there you'll need to
230 The one exception is the various *DIR install locations. Changing those
231 requires changes in genconfig.pl as well. Be really careful if you need to
232 change these, as they can cause some fairly subtle problems.
234 =head2 Socket Support (optional) for Perl on VMS
236 Perl includes a number of functions for IP sockets, which are available if
237 you choose to compile Perl with socket support. Since IP networking is an
238 optional addition to VMS, there are several different IP stacks available.
239 How well integrated they are into the system depends on the stack, your
240 version of VMS, and the version of your C compiler.
242 The most portable solution uses the SOCKETSHR library. In combination with
243 either UCX or NetLib, this supports all the major TCP stacks (Multinet,
244 Pathways, TCPWare, UCX, and CMU) on all versions of VMS Perl runs on, with
245 all the compilers on both VAX and Alpha. The socket interface is also
246 consistent across versions of VMS and C compilers. It has a problem with
247 UDP sockets when used with Multinet, though, so you should be aware of
250 The other solution available is to use the socket routines built into DEC
251 C. Which routines are available depend on the version of VMS you're
252 running, and require proper UCX emulation by your TCP/IP vendor.
253 Relatively current versions of Multinet, TCPWare, Pathway, and UCX all
254 provide the required libraries--check your manuals or release notes to see
255 if your version is new enough.
259 The configuration script will print out, at the very end, the MMS or MMK
260 command you need to compile perl. Issue it (exactly as printed) to start
263 Once you issue your MMS or MMK command, sit back and wait. Perl should
264 compile and link without a problem. If a problem does occur check the
265 "CAVEATS" section of this document. If that does not help send some
266 mail to the VMSPERL mailing list. Instructions are in the "Mailing Lists"
267 section of this document.
271 Once Perl has built cleanly you need to test it to make sure things work.
272 This step is very important since there are always things that can go wrong
273 somehow and yield a dysfunctional Perl for you.
275 Testing is very easy, though, as there's a full test suite in the perl
276 distribution. To run the tests, enter the *exact* MMS line you used to
277 compile Perl and add the word "test" to the end, like this:
279 If the compile command was:
283 then the test command ought to be:
287 MMS (or MMK) will run all the tests. This may take some time, as there are
288 a lot of tests. If any tests fail, there will be a note made on-screen.
289 At the end of all the tests, a summary of the tests, the number passed and
290 failed, and the time taken will be displayed.
292 If any tests fail, it means something is wrong with Perl. If the test suite
293 hangs (some tests can take upwards of two or three minutes, or more if
294 you're on an especially slow machine, depending on your machine speed, so
295 don't be hasty), then the test *after* the last one displayed failed. Don't
296 install Perl unless you're confident that you're OK. Regardless of how
297 confident you are, make a bug report to the VMSPerl mailing list.
299 If one or more tests fail, you can get more information on the failure by
300 issuing this command sequence:
302 @ [.VMS]TEST .typ "" "-v" [.subdir]test.T
304 where ".typ" is the file type of the Perl images you just built (if you
305 didn't do anything special, use .EXE), and "[.subdir]test.T" is the test
306 that failed. For example, with a normal Perl build, if the test indicated
307 that [.op]time failed, then you'd do this:
309 @ [.VMS]TEST .EXE "" "-v" [.OP]TIME.T
311 When you send in a bug report for failed tests, please include the output
312 from this command, which is run from the main source directory:
316 Note that -"V" really is a capital V in double quotes. This will dump out a
317 couple of screens worth of configuration information, and can help us
318 diagnose the problem. If (and only if) that did not work then try enclosing
323 If (and only if) that did not work then try enclosing the output of:
327 You may also be asked to provide your C compiler version ("CC/VERSION NL:"
328 with DEC C, "gcc --version" with GNU CC). To obtain the version of MMS or
329 MMK you are running try "MMS/ident" or "MMK /ident". The GNU make version
330 can be identified with "make --version".
332 =head2 Cleaning up and starting fresh (optional) installing Perl on VMS
334 If you need to recompile from scratch, you have to make sure you clean up
335 first. There is a procedure to do it--enter the *exact* MMS line you used
336 to compile and add "realclean" at the end, like this:
338 if the compile command was:
342 then the cleanup command ought to be:
346 If you do not do this things may behave erratically during the subsequent
347 rebuild attempt. They might not, too, so it is best to be sure and do it.
349 =head1 Installing Perl
351 There are several steps you need to take to get Perl installed and
358 Check your default file protections with
360 SHOW PROTECTION /DEFAULT
362 and adjust if necessary with SET PROTECTION=(code)/DEFAULT.
366 Decide where you want Perl to be installed (unless you have already done so
367 by using the "prefix" configuration parameter -- see the example in the
368 "Configuring the Perl build" section).
370 The DCL script PERL_SETUP.COM that is written by CONFIGURE.COM will help you
371 with the definition of the PERL_ROOT and PERLSHR logical names and the PERL
372 foreign command symbol. Take a look at PERL_SETUP.COM and modify it if you
373 want to. The installation process will execute PERL_SETUP.COM and copy
374 files to the directory tree pointed to by the PERL_ROOT logical name defined
375 there, so make sure that you have write access to the parent directory of
376 what will become the root of your Perl installation.
380 Run the install script via:
388 If for some reason it complains about target INSTALL being up to date,
389 throw a /FORCE switch on the MMS or MMK command.
393 Copy PERL_SETUP.COM to a place accessible to your perl users.
397 COPY PERL_SETUP.COM SYS$LIBRARY:
399 If you want to have everyone on the system have access to perl
400 then add a line that reads
402 $ @sys$library:perl_setup
404 to SYS$MANAGER:SYLOGIN.COM.
406 Two alternatives to the foreign symbol would be to install PERL into
407 DCLTABLES.EXE (Check out the section "Installing Perl into DCLTABLES
408 (optional)" for more information), or put the image in a
409 directory that's in your DCL$PATH (if you're using VMS V6.2 or higher).
411 An alternative to having PERL_SETUP.COM define the PERLSHR logical name
412 is to simply copy it into the system shareable library directory with:
414 copy perl_root:[000000]perlshr.exe sys$share:
416 See also the "INSTALLing images (optional)" section.
418 =head2 Installing Perl into DCLTABLES (optional) on VMS
420 Execute the following command file to define PERL as a DCL command.
421 You'll need CMKRNL privilege to install the new dcltables.exe.
425 ! modify to reflect location of your perl.exe
428 image perl_root:[000000]perl.exe
431 $ set command perl /table=sys$common:[syslib]dcltables.exe -
432 /output=sys$common:[syslib]dcltables.exe
433 $ install replace sys$common:[syslib]dcltables.exe
436 =head2 INSTALLing Perl images (optional) on VMS
438 On systems that are using perl quite a bit, and particularly those with
439 minimal RAM, you can boost the performance of perl by INSTALLing it as
440 a known image. PERLSHR.EXE is typically larger than 3000 blocks
441 and that is a reasonably large amount of IO to load each time perl is
444 INSTALL ADD PERLSHR/SHARE
445 INSTALL ADD PERL/HEADER
447 should be enough for PERLSHR.EXE (/share implies /header and /open),
448 while /HEADER should do for PERL.EXE (perl.exe is not a shared image).
450 If your code 'use's modules, check to see if there is a shareable image for
451 them, too. In the base perl build, POSIX, IO, Fcntl, Opcode, SDBM_File,
452 DCLsym, and Stdio, and other extensions all have shared images that can be
455 How much of a win depends on your memory situation, but if you are firing
456 off perl with any regularity (like more than once every 20 seconds or so)
457 it is probably beneficial to INSTALL at least portions of perl.
459 While there is code in perl to remove privileges as it runs you are advised
460 to NOT INSTALL PERL.EXE with PRIVs!
462 =head2 Running h2ph to create perl header files (optional) on VMS
464 If using DEC C or Compaq C ensure that you have extracted loose versions
465 of your compiler's header or *.H files. Be sure to check the contents of:
467 SYS$LIBRARY:DECC$RTLDEF.TLB
468 SYS$LIBRARY:SYS$LIB_C.TLB
469 SYS$LIBRARY:SYS$STARLET_C.TLB
473 If using GNU cc then also check your GNU_CC:[000000...] tree for the locations
474 of the GNU cc headers.
476 =head1 Reporting Bugs
478 If you come across what you think might be a bug in Perl, please report
479 it. There's a script in PERL_ROOT:[UTILS], perlbug, that walks you through
480 the process of creating a bug report. This script includes details of your
481 installation, and is very handy. Completed bug reports should go to
486 Probably the single biggest gotcha in compiling Perl is giving the wrong
487 switches to MMS/MMK when you build. Use *exactly* what the configure.com
490 The next big gotcha is directory depth. Perl can create directories four,
491 five, or even six levels deep during the build, so you don't have to be
492 too deep to start to hit the RMS 8 level limit (for ODS 2 volumes which were
493 common on versions of VMS prior to V7.2 and even with V7.2 on the VAX).
496 DEFINE/TRANS=(CONC,TERM) PERLSRC "disk:[dir.dir.dir.perldir.]"
497 SET DEFAULT PERLSRC:[000000]
499 before building in cases where you have to unpack the distribution so deep
500 (note the trailing period in the definition of PERLSRC). Perl modules
501 from CPAN can be just as bad (or worse), so watch out for them, too. Perl's
502 configuration script will warn if it thinks you are too deep (at least on
503 a VAX or on Alpha versions of VMS prior to 7.2). But MakeMaker will not
504 warn you if you start out building a module too deep in a directory.
506 Be sure that the process that you use to build perl has a PGFLQ greater
507 than 100000. Be sure to have a correct local time zone to UTC offset
508 defined (in seconds) in the logical name SYS$TIMEZONE_DIFFERENTIAL before
509 running the regression test suite. The SYS$MANAGER:UTC$CONFIGURE_TDF.COM
510 procedure will help you set that logical for your system but may require
511 system privileges. For example, a location 5 hours west of UTC (such as
512 the US East coast while not on daylight savings time) would have:
514 DEFINE SYS$TIMEZONE_DIFFERENTIAL "-18000"
516 A final thing that causes trouble is leftover pieces from a failed
517 build. If things go wrong make sure you do a "(MMK|MMS|make) realclean"
520 =head2 DEC C issues with Perl on VMS
522 Note to DEC C users: Some early versions (pre-5.2, some pre-4. If you're DEC
523 C 5.x or higher, with current patches if any, you're fine) of the DECCRTL
524 contained a few bugs which affect Perl performance:
530 Newlines are lost on I/O through pipes, causing lines to run together.
531 This shows up as RMS RTB errors when reading from a pipe. You can
532 work around this by having one process write data to a file, and
533 then having the other read the file, instead of the pipe. This is
534 fixed in version 4 of DEC C.
538 The modf() routine returns a non-integral value for some values above
539 INT_MAX; the Perl "int" operator will return a non-integral value in
540 these cases. This is fixed in version 4 of DEC C.
544 On the AXP, if SYSNAM privilege is enabled, the CRTL chdir() routine
545 changes the process default device and directory permanently, even
546 though the call specified that the change should not persist after
547 Perl exited. This is fixed by DEC CSC patch ALPACRT04_061 or later.
550 http://ftp.support.compaq.com/patches/.new/openvms.shtml
554 Please note that in later versions "DEC C" may also be known as
557 =head2 GNU issues with Perl on VMS
559 It has been a while since the GNU utilities such as GCC or GNU make
560 were used to build perl on VMS. Hence they may require a great deal
561 of source code modification to work again.
563 http://slacvx.slac.stanford.edu/HELP/GCC
564 http://www.progis.de/
565 http://www.lp.se/products/gnu.html
567 =head2 Floating Point Considerations
569 Prior to 5.8.0, Perl simply accepted the default floating point options of the
570 C compiler, namely representing doubles with D_FLOAT on VAX and G_FLOAT on
571 Alpha. Single precision floating point values are represented in F_FLOAT
572 format when either D_FLOAT or G_FLOAT is in use for doubles. Beginning with
573 5.8.0, Alpha builds now use IEEE floating point formats by default, which in
574 VMS parlance are S_FLOAT for singles and T_FLOAT for doubles. IEEE is not
575 available on VAX, so F_FLOAT and D_FLOAT remain the defaults for singles and
576 doubles respectively. The available non-default options are G_FLOAT on VAX
577 and D_FLOAT or G_FLOAT on Alpha.
579 The use of IEEE on Alpha introduces NaN, infinity, and denormalization
580 capabilities not available with D_FLOAT and G_FLOAT. When using one of those
581 non-IEEE formats, silent underflow and overflow are emulated in the conversion
582 of strings to numbers, but it is preferable to get the real thing by using
585 Regardless of what floating point format you consider preferable, be aware
586 that the choice may have an impact on compatibility with external libraries,
587 such as database interfaces, and with existing data, such as data created with
588 the C<pack> function and written to disk, or data stored via the Storable
589 extension. For example, a C<pack("d", $foo)")> will create a D_FLOAT,
590 G_FLOAT, or T_FLOAT depending on what your Perl was configured with. When
591 written to disk, the value can only be retrieved later by a Perl configured
592 with the same floating point option that was in effect when it was created.
594 To obtain a non-IEEE build on Alpha, simply answer no to the "Use IEEE math?"
595 question during the configuration. To obtain an option different from the C
596 compiler default on either VAX or Alpha, put in the option that you want in
597 answer to the "Any additional cc flags?" question. For example, to obtain a
598 G_FLOAT build on VAX, put in C</FLOAT=G_FLOAT>.
600 =head2 Multinet issues with Perl on VMS
602 Prior to the release of Perl 5.8.0 it was noted that the regression
603 test for lib/Net/hostent (in file [.lib.Net]hostent.t) will fail owing
604 to problems with the hostent structure returned by C calls to either
605 gethostbyname() or gethostbyaddr() using DEC or Compaq C with a
606 Multinet TCP/IP stack. The problem was noted in Multinet 4.3A
607 using either Compaq C 6.5 or DEC C 6.0, and with Multinet 4.2A
608 using DEC C 5.2, but could easily affect other versions of Multinet.
609 Process Software Inc. has acknowledged a bug in the Multinet version
610 of UCX$IPC_SHR and has provided an ECO for it. The ECO is called
611 UCX_LIBRARY_EMULATION-010_A044 and is available from:
613 http://www.multinet.process.com/eco.html
615 As of this writing, the ECO is only available for Multinet versions
616 4.3A and later. You may determine the version of Multinet that you
617 are running using the command:
619 multinet show /version
621 from the DCL command prompt.
623 If the ECO is unavailable for your version of Multinet and you are
624 unable to upgrade, you might try using Perl programming constructs
627 $address = substr($gethostbyname_addr,0,4);
629 to temporarily work around the problem, or if you are brave
630 and do not mind the possibility of breaking IPv6 addresses,
631 you might modify the pp_sys.c file to add an ad-hoc correction
635 --- pp_sys.c;1 Thu May 30 14:42:17 2002
636 +++ pp_sys.c Thu May 30 12:54:02 2002
637 @@ -4684,6 +4684,10 @@
642 + hent->h_length = 4;
645 if (GIMME != G_ARRAY) {
646 PUSHs(sv = sv_newmortal());
649 then re-compile and re-test your perl. After the installation
650 of the Multinet ECO you ought to back out any such changes though.
654 There are several mailing lists available to the Perl porter. For VMS
655 specific issues (including both Perl questions and installation problems)
656 there is the VMSPERL mailing list. It is usually a low-volume (10-12
657 messages a week) mailing list.
659 To subscribe, send a mail message to VMSPERL-SUBSCRIBE@PERL.ORG. The VMSPERL
660 mailing list address is VMSPERL@PERL.ORG. Any mail sent there gets echoed
661 to all subscribers of the list. There is a searchable archive of the list
664 http://www.xray.mpe.mpg.de/mailing-lists/vmsperl/
666 To unsubscribe from VMSPERL send a message to VMSPERL-UNSUBSCRIBE@PERL.ORG.
667 Be sure to do so from the subscribed account that you are canceling.
669 =head2 Web sites for Perl on VMS
671 Vmsperl pages on the web include:
673 http://www.sidhe.org/vmsperl/index.html
674 http://www.crinoid.com/
675 http://duphy4.physics.drexel.edu/pub/cgi_info.htmlx
676 http://www.cpan.org/modules/by-module/VMS/
677 http://www.xray.mpe.mpg.de/mailing-lists/vmsperl/
678 http://www.best.com/~pvhp/vms/
679 http://www-ang.kfunigraz.ac.at/~binder/perl.html
680 http://lists.perl.org/showlist.cgi?name=vmsperl
681 http://archive.develooper.com/vmsperl@perl.org/
682 http://www.openvms.compaq.com/openvms/products/ips/apache/csws_modperl.html
686 Perl information for users and programmers about the port of perl to VMS is
687 available from the [.VMS]PERLVMS.POD file that gets installed as L<perlvms>.
688 For administrators the perlvms document also includes a detailed discussion
689 of extending vmsperl with CPAN modules after Perl has been installed.
693 Revised 10-October-2001 by Craig Berry craigberry@mac.com.
694 Revised 25-February-2000 by Peter Prymmer pvhp@best.com.
695 Revised 27-October-1999 by Craig Berry craigberry@mac.com.
696 Revised 01-March-1999 by Dan Sugalski dan@sidhe.org.
697 Originally by Charles Bailey bailey@newman.upenn.edu.
699 =head1 ACKNOWLEDGEMENTS
701 A real big thanks needs to go to Charles Bailey
702 bailey@newman.upenn.edu, who is ultimately responsible for Perl 5.004
703 running on VMS. Without him, nothing the rest of us have done would be at
706 There are, of course, far too many people involved in the porting and testing
707 of Perl to mention everyone who deserves it, so please forgive us if we've
708 missed someone. That said, special thanks are due to the following:
710 Tim Adye T.J.Adye@rl.ac.uk
711 for the VMS emulations of getpw*()
712 David Denholm denholm@conmat.phys.soton.ac.uk
713 for extensive testing and provision of pipe and SocketShr code,
714 Mark Pizzolato mark@infocomm.com
715 for the getredirection() code
716 Rich Salz rsalz@bbn.com
717 for readdir() and related routines
718 Peter Prymmer pvhp@best.com
719 for extensive testing, as well as development work on
720 configuration and documentation for VMS Perl,
721 Dan Sugalski dan@sidhe.org
722 for extensive contributions to recent version support,
723 development of VMS-specific extensions, and dissemination
724 of information about VMS Perl,
725 the Stanford Synchrotron Radiation Laboratory and the
726 Laboratory of Nuclear Studies at Cornell University for
727 the opportunity to test and develop for the AXP,
728 John Hasstedt John.Hasstedt@sunysb.edu
729 for VAX VMS V7.2 support
731 and to the entire VMSperl group for useful advice and suggestions. In
732 addition the perl5-porters deserve credit for their creativity and
733 willingness to work with the VMS newcomers. Finally, the greatest debt of
734 gratitude is due to Larry Wall larry@wall.org, for having the ideas which
735 have made our sleepless nights possible.