PERL V4.0 Patchlevel 19 for VAX/VMS

This is more like a hacker's guide than a user's README file.

This port of Perl for VMS has been done under VAX/VMS V5.4-2 using the
VAX C Compiler version 2.3.

If you got the source kit, the two command files COMPILE.COM and
LINK.COM should perform the necessary work to build the executable
yourself.

VMS support is only rudimentary.  There is no emulation of pipes, so
many of the standard perl features (namely, and most importantly,
filename expansions) are not available under VMS.  If you are brave,
you might want to have a look into eval.c and try to find a way how to
implement filename globbing under VMS.

perl seems to have some difficulties using the VAX C run time library,
especially in respect to standard I/O.  In particular, ftell and fseek
do not seem to work properly on files created with perl's own open()
routine.  It might be a good idea to extend perl's open() routine to
accept arguments similar to VAX C's fopen() routine, which would give
the programmer a more fine-grained control over the RMS attributes of
created files.  Anyway, for the time being you can always create your
files from within the DCL procedure which calls perl afterwards.  This
does seem the best approach after all, since adding *complete* VMS
support to perl would require lot's of changes in perl's internal
workings *and* a lot more than RMS support.

I have not attempted to keep the distribution complete, so you might
want to look into the unix perl kit for some further supporting files.
You might also use this port as a starting point for a vms/
subdirectory in the standard perl distribution.  I currently don't
have the time to do that, sorry.  If you intend to merge the two, be
advised to run both versions through indent (I reformatted part of the
files to fit my emacs c-mode settings) as well as running diff against
a vanilla perl V4.0 pl 19 distribution - I had to change some places
in the mainstream code without embracing them between #if defined(VMS)
and #endif.  In particular, I swapped the nelems and size arguments to
fwrite in some places, which resulted in a big performance boost of
perl under VMS (and is transparent to Unix sites, as far as I can
tell).

What I use perl for is report writing, and that has been the reason
for me porting it to VMS.  I use a user subroutine module to interface
perl to RDB/VMS, which in effect makes SQL accessible from within
perl.  The stuff needed to get this running is contained in a seperate
save set which should be available for anonymous ftp at the site you
got this kit from.  If it's not there, try getting it from
ftp.artcom.de, but that systems' internet connection is rather slow.
To get the RDB interface running, you need a working installation of
the GNU C++ compiler and the GNU C++ library.  I only used V1.39 so
far, and I'm not sure whether it will work with more recent version.

I hope you enjoy using perl under VMS as much as I do.  If you decide
to make the port more complete, please tell me.  It could be that I
have some time left to spend on perl, so it might be a good idea to
coordinate the efforts.

-Hans

Hans Huebner - hans@artcom.de

