X-Git-Url: https://perl5.git.perl.org/perl5.git/blobdiff_plain/87275199ef473a0bd08ce6f46db30d4d432f4876..a4bf32d53b7a7eecac9d0d73294ba4e62515c7b5:/pod/perlport.pod diff --git a/pod/perlport.pod b/pod/perlport.pod index 6837b4c..d1887bf 100644 --- a/pod/perlport.pod +++ b/pod/perlport.pod @@ -75,7 +75,7 @@ This information should not be considered complete; it includes possibly transient information about idiosyncrasies of some of the ports, almost all of which are in a state of constant evolution. Thus, this material should be considered a perpetual work in progress -(EIMG SRC="yellow_sign.gif" ALT="Under Construction"E). +(Under Construction). =head1 ISSUES @@ -90,7 +90,7 @@ Perl uses C<\n> to represent the "logical" newline, where what is logical may depend on the platform in use. In MacPerl, C<\n> always means C<\015>. In DOSish perls, C<\n> usually means C<\012>, but when accessing a file in "text" mode, STDIO translates it to (or -from) C<\015\012>, depending on whether your reading or writing. +from) C<\015\012>, depending on whether you're reading or writing. Unix does the same thing on ttys in canonical mode. C<\015\012> is commonly referred to as CRLF. @@ -180,11 +180,26 @@ usually either "live" via network connection, or by storing the numbers to secondary storage such as a disk file or tape. Conflicting storage orders make utter mess out of the numbers. If a -little-endian host (Intel, Alpha) stores 0x12345678 (305419896 in -decimal), a big-endian host (Motorola, MIPS, Sparc, PA) reads it as -0x78563412 (2018915346 in decimal). To avoid this problem in network -(socket) connections use the C and C formats C -and C, the "network" orders. These are guaranteed to be portable. +little-endian host (Intel, VAX) stores 0x12345678 (305419896 in +decimal), a big-endian host (Motorola, Sparc, PA) reads it as +0x78563412 (2018915346 in decimal). Alpha and MIPS can be either: +Digital/Compaq used/uses them in little-endian mode; SGI/Cray uses +them in big-endian mode. To avoid this problem in network (socket) +connections use the C and C formats C and C, the +"network" orders. These are guaranteed to be portable. + +You can explore the endianness of your platform by unpacking a +data structure packed in native format such as: + + print unpack("h*", pack("s2", 1, 2)), "\n"; + # '10002000' on e.g. Intel x86 or Alpha 21064 in little-endian mode + # '00100020' on e.g. Motorola 68040 + +If you need to distinguish between endian architectures you could use +either of the variables set like so: + + $is_big_endian = unpack("h*", pack("s", 1)) =~ /01/; + $is_little_endian = unpack("h*", pack("s", 1)) =~ /^1/; Differing widths can cause truncation even between platforms of equal endianness. The platform of shorter width loses the upper parts of the @@ -204,7 +219,7 @@ So, it is reasonably safe to assume that all platforms support the notion of a "path" to uniquely identify a file on the system. How that path is really written, though, differs considerably. -Atlhough similar, file path specifications differ between Unix, +Although similar, file path specifications differ between Unix, Windows, S, OS/2, VMS, VOS, S, and probably others. Unix, for example, is one of the few OSes that has the elegant idea of a single root directory. @@ -242,9 +257,13 @@ to be running the program. $file = catfile(curdir(), 'temp', 'file.txt'); # on Unix and Win32, './temp/file.txt' # on Mac OS, ':temp:file.txt' + # on VMS, '[.temp]file.txt' File::Spec is available in the standard distribution as of version -5.004_05. +5.004_05. File::Spec::Functions is only in File::Spec 0.7 and later, +and some versions of perl come with version 0.6. If File::Spec +is not updated to 0.7 or later, you must use the object-oriented +interface from File::Spec (or upgrade File::Spec). In general, production code should not have file paths hardcoded. Making them user-supplied or read from a configuration file is @@ -286,15 +305,15 @@ first 8 characters. Whitespace in filenames is tolerated on most systems, but not all. Many systems (DOS, VMS) cannot have more than one C<.> in their filenames. -Don't assume C> won't be the first character of a filename. -Always use C> explicitly to open a file for reading, +Don't assume C<< > >> won't be the first character of a filename. +Always use C<< < >> explicitly to open a file for reading, unless you want the user to be able to specify a pipe open. open(FILE, "< $existing_file") or die $!; If filenames might use strange characters, it is safest to open it with C instead of C. C is magic and can -translate characters like C>, C>, and C<|>, which may +translate characters like C<< > >>, C<< < >>, and C<|>, which may be the wrong thing to do. (Sometimes, though, it's the right thing.) =head2 System Interaction @@ -317,7 +336,7 @@ Don't count on a specific environment variable existing in C<%ENV>. Don't count on C<%ENV> entries being case-sensitive, or even case-preserving. -Don't count on signals for anything. +Don't count on signals or C<%SIG> for anything. Don't count on filename globbing. Use C, C, and C instead. @@ -338,7 +357,7 @@ Commands that launch external processes are generally supported on most platforms (though many of them do not support any type of forking). The problem with using them arises from what you invoke them on. External tools are often named differently on different -platforms, may not be available in the same location, migth accept +platforms, may not be available in the same location, might accept different arguments, can behave differently, and often present their results in a platform-dependent way. Thus, you should seldom depend on them to produce consistent results. (Then again, if you're calling @@ -511,7 +530,7 @@ a given module works on a given platform. =item Mailing list: cpan-testers@perl.org -=item Testing results: C +=item Testing results: http://testers.cpan.org/ =back @@ -534,10 +553,11 @@ edited after the fact. Perl works on a bewildering variety of Unix and Unix-like platforms (see e.g. most of the files in the F directory in the source code kit). On most of these systems, the value of C<$^O> (hence C<$Config{'osname'}>, -too) is determined by lowercasing and stripping punctuation from the first -field of the string returned by typing C (or a similar command) -at the shell prompt. Here, for example, are a few of the more popular -Unix flavors: +too) is determined either by lowercasing and stripping punctuation from the +first field of the string returned by typing C (or a similar command) +at the shell prompt or by testing the file system for the presence of +uniquely named files such as a kernel or header file. Here, for example, +are a few of the more popular Unix flavors: uname $^O $Config{'archname'} -------------------------------------------- @@ -546,11 +566,16 @@ Unix flavors: dgux dgux AViiON-dgux DYNIX/ptx dynixptx i386-dynixptx FreeBSD freebsd freebsd-i386 + Linux linux arm-linux Linux linux i386-linux Linux linux i586-linux Linux linux ppc-linux HP-UX hpux PA-RISC1.1 IRIX irix irix + Mac OS X rhapsody rhapsody + MachTen PPC machten powerpc-machten + NeXT 3 next next-fat + NeXT 4 next OPENSTEP-Mach openbsd openbsd i386-openbsd OSF1 dec_osf alpha-dec_osf reliantunix-n svr4 RM400-svr4 @@ -625,20 +650,48 @@ DOSish perls are as follows: Windows NT MSWin32 MSWin32-x86 Windows NT MSWin32 MSWin32-ALPHA Windows NT MSWin32 MSWin32-ppc + Cygwin cygwin Also see: =over 4 -=item The djgpp environment for DOS, C +=item * + +The djgpp environment for DOS, http://www.delorie.com/djgpp/ +and L. + +=item * + +The EMX environment for DOS, OS/2, etc. emx@iaehv.nl, +http://www.leo.org/pub/comp/os/os2/leo/gnu/emx+gcc/index.html or +ftp://hobbes.nmsu.edu/pub/os2/dev/emx. Also L. + +=item * + +Build instructions for Win32 in L, or under the Cygnus environment +in L. + +=item * -=item The EMX environment for DOS, OS/2, etc. C, -C or -C +The C modules in L. -=item Build instructions for Win32, L. +=item * + +The ActiveState Pages, http://www.activestate.com/ + +=item * + +The Cygwin environment for Win32; F (installed +as L), http://sources.redhat.com/cygwin/ + +=item * + +The U/WIN environment for Win32, + -=item The ActiveState Pages, C =back @@ -711,17 +764,23 @@ Also see: =over 4 -=item The MacPerl Pages, C. +=item * + +The MacPerl Pages, http://www.macperl.com/ . + +=item * -=item The MacPerl mailing lists, C. +The MacPerl mailing lists, http://www.macperl.org/ . -=item MacPerl Module Porters, C. +=item * + +MacPerl Module Porters, http://pudge.net/mmp/ . =back =head2 VMS -Perl on VMS is discussed in F in the perl distribution. +Perl on VMS is discussed in L in the perl distribution. Perl on VMS can accept either VMS- or Unix-style file specifications as in either of the following: @@ -756,7 +815,7 @@ you are so inclined. For example: $ endif Do take care with C<$ ASSIGN/nolog/user SYS$COMMAND: SYS$INPUT> if your -perl-in-DCL script expects to do things like C<$read = ESTDINE;>. +perl-in-DCL script expects to do things like C<< $read = ; >>. Filenames are in the format "name.extension;version". The maximum length for filenames is 39 characters, and the maximum length for @@ -783,9 +842,9 @@ non-VMS platforms and can be helpful for conversions to and from RMS native formats. What C<\n> represents depends on the type of file opened. It could -be C<\015>, C<\012>, C<\015\012>, or nothing. Reading from a file -translates newlines to C<\012>, unless C was executed on that -handle, just like DOSish perls. +be C<\015>, C<\012>, C<\015\012>, or nothing. The VMS::Stdio module +provides access to the special fopen() requirements of files with unusual +attributes on VMS. TCP/IP stacks are optional on VMS, so socket routines might not be implemented. UDP sockets may not be supported. @@ -813,21 +872,27 @@ Also see: =over 4 -=item L +=item * + +F (installed as L), L -=item vmsperl list, C +=item * -Put the words C in message body. +vmsperl list, majordomo@perl.org -=item vmsperl on the web, C +(Put the words C in message body.) + +=item * + +vmsperl on the web, http://www.sidhe.org/vmsperl/index.html =back =head2 VOS -Perl on VOS is discussed in F in the perl distribution. -Perl on VOS can accept either VOS- or Unix-style file -specifications as in either of the following: +Perl on VOS is discussed in F in the perl distribution +(installed as L). Perl on VOS can accept either VOS- or +Unix-style file specifications as in either of the following: $ perl -ne "print if /perl_setup/i" >system>notices $ perl -ne "print if /perl_setup/i" /system/notices @@ -840,20 +905,20 @@ Even though VOS allows the slash character to appear in object names, because the VOS port of Perl interprets it as a pathname delimiting character, VOS files, directories, or links whose names contain a slash character cannot be processed. Such files must be -renamed before they can be processed by Perl. +renamed before they can be processed by Perl. Note that VOS limits +file names to 32 or fewer characters. -The following C functions are unimplemented on VOS, and any attempt by -Perl to use them will result in a fatal error message and an immediate -exit from Perl: dup, do_aspawn, do_spawn, fork, waitpid. Once these -functions become available in the VOS POSIX.1 implementation, you can -either recompile and rebind Perl, or you can download a newer port from -ftp.stratus.com. +See F for restrictions that apply when Perl is built +with the alpha version of VOS POSIX.1 support. + +Perl on VOS is built without any extensions and does not support +dynamic loading. The value of C<$^O> on VOS is "VOS". To determine the architecture that you are running on without resorting to loading all of C<%Config> you -can examine the content of the C<@INC> array like so: +can examine the content of the @INC array like so: - if (grep(/VOS/, @INC)) { + if ($^O =~ /VOS/) { print "I'm on a Stratus box!\n"; } else { print "I'm not on a Stratus box!\n"; @@ -864,40 +929,48 @@ can examine the content of the C<@INC> array like so: print "This box is a Stratus XA/R!\n"; } elsif (grep(/7100/, @INC)) { - print "This box is a Stratus HP 7100 or 8000!\n"; + print "This box is a Stratus HP 7100 or 8xxx!\n"; } elsif (grep(/8000/, @INC)) { - print "This box is a Stratus HP 8000!\n"; + print "This box is a Stratus HP 8xxx!\n"; } else { - print "This box is a Stratus 68K...\n"; + print "This box is a Stratus 68K!\n"; } Also see: =over 4 -=item L +=item * + +F -=item VOS mailing list +=item * + +The VOS mailing list. There is no specific mailing list for Perl on VOS. You can post comments to the comp.sys.stratus newsgroup, or subscribe to the general Stratus mailing list. Send a letter with "Subscribe Info-Stratus" in the message body to majordomo@list.stratagy.com. -=item VOS Perl on the web at C +=item * + +VOS Perl on the web at http://ftp.stratus.com/pub/vos/vos.html =back =head2 EBCDIC Platforms Recent versions of Perl have been ported to platforms such as OS/400 on -AS/400 minicomputers as well as OS/390 & VM/ESA for IBM Mainframes. Such -computers use EBCDIC character sets internally (usually Character Code -Set ID 00819 for OS/400 and IBM-1047 for OS/390 & VM/ESA). On -the mainframe perl currently works under the "Unix system services -for OS/390" (formerly known as OpenEdition) and VM/ESA OpenEdition. +AS/400 minicomputers as well as OS/390, VM/ESA, and BS2000 for S/390 +Mainframes. Such computers use EBCDIC character sets internally (usually +Character Code Set ID 0037 for OS/400 and either 1047 or POSIX-BC for S/390 +systems). On the mainframe perl currently works under the "Unix system +services for OS/390" (formerly known as OpenEdition), VM/ESA OpenEdition, or +the BS200 POSIX-BC system (BS2000 is supported in perl 5.6 and greater). +See L for details. As of R2.5 of USS for OS/390 and Version 2.3 of VM/ESA these Unix sub-systems do not support the C<#!> shebang trick for script invocation. @@ -911,6 +984,10 @@ similar to the following simple script: print "Hello from perl!\n"; +OS/390 will support the C<#!> shebang trick in release 2.8 and beyond. +Calls to C and backticks can use POSIX shell syntax on all +S/390 systems. + On the AS/400, if PERL5 is in your library list, you may need to wrap your perl scripts in a CL procedure to invoke them like so: @@ -935,9 +1012,14 @@ translate the C<\n> in the following statement to its ASCII equivalent print "Content-type: text/html\r\n\r\n"; -The value of C<$^O> on OS/390 is "os390". +The values of C<$^O> on some of these platforms includes: -The value of C<$^O> on VM/ESA is "vmesa". + uname $^O $Config{'archname'} + -------------------------------------------- + OS/390 os390 os390 + OS400 os400 os400 + POSIX-BC posix-bc BS2000-posix-bc + VM/ESA vmesa vmesa Some simple tricks for determining if you are running on an EBCDIC platform could include any of the following (perhaps all): @@ -957,13 +1039,24 @@ Also see: =over 4 -=item perl-mvs list +=item * + +* + +L, F, F, F, +L. + +=item * The perl-mvs@perl.org list is for discussion of porting issues as well as general usage issues for all EBCDIC Perls. Send a message body of "subscribe perl-mvs" to majordomo@perl.org. -=item AS/400 Perl information at C +=item * + +AS/400 Perl information at +http://as400.rochester.ibm.com/ +as well as on CPAN in the F directory. =back @@ -1008,9 +1101,9 @@ C until a name is made that points to an object on disk. Writing to a new file C would be allowed only if C contains a single item list. The filesystem will also expand system variables in filenames if enclosed in angle brackets, so -CSystem$DirE.Modules> would look for the file +C<< .Modules >> would look for the file S>. The obvious implication of this is -that BE>> and should +that B >>> and should be protected when C is used for input. Because C<.> was in use as a directory separator and filenames could not @@ -1050,11 +1143,11 @@ library emulates Unix filehandles. Consequently, you can't rely on passing C, C, or C to your children. The desire of users to express filenames of the form -CFoo$DirE.Bar> on the command line unquoted causes problems, +C<< .Bar >> on the command line unquoted causes problems, too: C<``> command output capture has to perform a guessing game. It -assumes that a string C[^EE]+\$[^EE]E> is a +assumes that a string C<< <[^<>]+\$[^<>]> >> is a reference to an environment variable, whereas anything else involving -C> or C> is redirection, and generally manages to be 99% +C<< < >> or C<< > >> is redirection, and generally manages to be 99% right. Of course, the problem remains that scripts cannot rely on any Unix tools being available, or that any tools found have Unix-like command line arguments. @@ -1081,20 +1174,46 @@ for the likes of: aos, Atari ST, lynxos, riscos, Novell Netware, Tandem Guardian, I (Yes, we know that some of these OSes may fall under the Unix category, but we are not a standards body.) +Some approximate operating system names and their C<$^O> values +in the "OTHER" category include: + + OS $^O $Config{'archname'} + ------------------------------------------ + Amiga DOS amigaos m68k-amigos + MPE/iX mpeix PA-RISC1.1 + See also: =over 4 -=item Atari, Guido Flohr's page C +=item * + +Amiga, F (installed as L). + +=item * -=item HP 300 MPE/iX C +Atari, F and Guido Flohr's web page +http://stud.uni-sb.de/~gufl0000/ -=item Novell Netware +=item * + +Be OS, F + +=item * + +HP 300 MPE/iX, F and Mark Bixby's web page +http://www.cccd.edu/~markb/perlix.html + +=item * A free perl5-based PERL.NLM for Novell Netware is available in -precompiled binary and source code form from C +precompiled binary and source code form from http://www.novell.com/ as well as from CPAN. +=item + +Plan 9, F + =back =head1 FUNCTION IMPLEMENTATIONS @@ -1162,6 +1281,12 @@ suffixes. C<-S> is meaningless. (Win32) C<-x> (or C<-X>) determine if a file has an executable file type. (S) +=item alarm SECONDS + +=item alarm + +Not implemented. (Win32) + =item binmode FILEHANDLE Meaningless. (S, S) @@ -1226,6 +1351,9 @@ Not implemented. (S) Implemented via Spawn. (VM/ESA) +Does not automatically flush output handles on some platforms. +(SunOS, Solaris, HP-UX) + =item fcntl FILEHANDLE,FUNCTION,SCALAR Not implemented. (Win32, VMS) @@ -1238,7 +1366,12 @@ Available only on Windows NT (not on Windows 95). (Win32) =item fork -Not implemented. (S, Win32, AmigaOS, S, VOS, VM/ESA) +Not implemented. (S, AmigaOS, S, VOS, VM/ESA) + +Emulated using multiple interpreters. See L. (Win32) + +Does not automatically flush output handles on some platforms. +(SunOS, Solaris, HP-UX) =item getlogin @@ -1342,11 +1475,11 @@ Not implemented. (Plan9, Win32, S) =item endpwent -Not implemented. (S, Win32, VM/ESA) +Not implemented. (S, MPE/iX, VM/ESA, Win32) =item endgrent -Not implemented. (S, Win32, VMS, S, VM/ESA) +Not implemented. (S, MPE/iX, S, VM/ESA, VMS, Win32) =item endhostent @@ -1375,14 +1508,8 @@ Not implemented. (S, Plan9) Globbing built-in, but only C<*> and C metacharacters are supported. (S) -Features depend on external perlglob.exe or perlglob.bat. May be -overridden with something like File::DosGlob, which is recommended. -(Win32) - -Globbing built-in, but only C<*> and C metacharacters are supported. -Globbing relies on operating system calls, which may return filenames -in any order. As most filesystems are case-insensitive, even "sorted" -filenames will not be in case-sensitive order. (S) +This operator is implemented via the File::Glob extension on most +platforms. See L for portability information. =item ioctl FILEHANDLE,FUNCTION,SCALAR @@ -1393,21 +1520,28 @@ in the Winsock API does. (Win32) Available only for socket handles. (S) -=item kill LIST +=item kill SIGNAL, LIST Not implemented, hence not useful for taint checking. (S, S) -Available only for process handles returned by the C -method of spawning a process. (Win32) +C doesn't have the semantics of C, i.e. it doesn't send +a signal to the identified process like it does on Unix platforms. +Instead C terminates the process identified by $pid, +and makes it exit immediately with exit status $sig. As in Unix, if +$sig is 0 and the specified process exists, it returns true without +actually terminating it. (Win32) =item link OLDFILE,NEWFILE -Not implemented. (S, Win32, VMS, S) +Not implemented. (S, MPE/iX, VMS, S) Link count not updated because hard links are not quite that hard (They are sort of half-way between hard and soft links). (AmigaOS) +Hard links are implemented on Win32 (Windows NT and Windows 2000) +under NTFS only. + =item lstat FILEHANDLE =item lstat EXPR @@ -1416,7 +1550,7 @@ Link count not updated because hard links are not quite that hard Not implemented. (VMS, S) -Return values may be bogus. (Win32) +Return values (especially for device and inode) may be bogus. (Win32) =item msgctl ID,CMD,ARG @@ -1437,6 +1571,9 @@ The C<|> variants are supported only if ToolServer is installed. open to C<|-> and C<-|> are unsupported. (S, Win32, S) +Opening a process does not automatically flush output handles on some +platforms. (SunOS, Solaris, HP-UX) + =item pipe READHANDLE,WRITEHANDLE Not implemented. (S) @@ -1455,6 +1592,8 @@ Only implemented on sockets. (Win32) Only reliable on sockets. (S) +Note that the C form is generally portable. + =item semctl ID,SEMNUM,CMD,ARG =item semget KEY,NSEMS,FLAGS @@ -1463,6 +1602,10 @@ Only reliable on sockets. (S) Not implemented. (S, Win32, VMS, S, VOS) +=item setgrent + +Not implemented. (MPE/iX, Win32) + =item setpgrp PID,PGRP Not implemented. (S, Win32, VMS, S, VOS) @@ -1471,6 +1614,10 @@ Not implemented. (S, Win32, VMS, S, VOS) Not implemented. (S, Win32, VMS, S, VOS) +=item setpwent + +Not implemented. (MPE/iX, Win32) + =item setsockopt SOCKET,LEVEL,OPTNAME,OPTVAL Not implemented. (S, Plan9) @@ -1495,6 +1642,10 @@ Not implemented. (S, Win32, VMS, S, VOS, VM/ESA) =item stat +Platforms that do not have rdev, blksize, or blocks will return these +as '', so numeric comparison or manipulation of these fields may cause +'not numeric' warnings. + mtime and atime are the same thing, and ctime is creation time instead of inode change time. (S) @@ -1505,6 +1656,9 @@ device and inode are not necessarily reliable. (VMS) mtime, atime and ctime all return the last modification time. Device and inode are not necessarily reliable. (S) +dev, rdev, blksize, and blocks are not available. inode is not +meaningful and will differ between stat calls on the same file. (os2) + =item symlink OLDFILE,NEWFILE Not implemented. (Win32, VMS, S) @@ -1528,11 +1682,14 @@ As an optimization, may not call the command shell specified in C<$ENV{PERL5SHELL}>. C spawns an external process and immediately returns its process designator, without waiting for it to terminate. Return value may be used subsequently -in C or C. (Win32) +in C or C. Failure to spawn() a subprocess is indicated +by setting $? to "255 << 8". C<$?> is set in a way compatible with +Unix (i.e. the exitstatus of the subprocess is obtained by "$? >> 8", +as described in the documentation). (Win32) There is no shell to process metacharacters, and the native standard is to pass a command line terminated by "\n" "\r" or "\0" to the spawned -program. Redirection such as C foo> is performed (if at all) by +program. Redirection such as C<< > foo >> is performed (if at all) by the run time library of the spawned program. C I will call the Unix emulation library's C emulation, which attempts to provide emulation of the stdin, stdout, stderr in force in the parent, providing @@ -1543,15 +1700,19 @@ of a child Unix program will exists. Mileage B vary. (S) Far from being POSIX compliant. Because there may be no underlying /bin/sh tries to work around the problem by forking and execing the first token in its argument string. Handles basic redirection -("E" or "E") on its own behalf. (MiNT) +("<" or ">") on its own behalf. (MiNT) + +Does not automatically flush output handles on some platforms. +(SunOS, Solaris, HP-UX) =item times Only the first entry returned is nonzero. (S) -"cumulative" times will be bogus. On anything other than Windows NT, -"system" time will be bogus, and "user" time is actually the time -returned by the clock() function in the C runtime library. (Win32) +"cumulative" times will be bogus. On anything other than Windows NT +or Windows 2000, "system" time will be bogus, and "user" time is +actually the time returned by the clock() function in the C runtime +library. (Win32) Not useful. (S) @@ -1594,7 +1755,7 @@ two seconds. (Win32) Not implemented. (S, VOS) Can only be applied to process handles returned for processes spawned -using C. (Win32) +using C or pseudo processes created with C. (Win32) Not useful. (S) @@ -1604,6 +1765,24 @@ Not useful. (S) =over 4 +=item v1.47, 22 March 2000 + +Various cleanups from Tom Christiansen, including migration of +long platform listings from L. + +=item v1.46, 12 February 2000 + +Updates for VOS and MPE/iX. (Peter Prymmer) Other small changes. + +=item v1.45, 20 December 1999 + +Small changes from 5.005_63 distribution, more changes to EBCDIC info. + +=item v1.44, 19 July 1999 + +A bunch of updates from Peter Prymmer for C<$^O> values, +endianness, File::Spec, VMS, BS2000, OS/400. + =item v1.43, 24 May 1999 Added a lot of cleaning up from Tom Christiansen. @@ -1616,7 +1795,7 @@ Added notes about tests, sprintf/printf, and epoch offsets. Lots more little changes to formatting and content. -Added a bunch of <$^O> and related values +Added a bunch of C<$^O> and related values for various platforms; fixed mail and web addresses, and added and changed miscellaneous notes. (Peter Prymmer) @@ -1666,41 +1845,197 @@ First public release with perl5.005. =back +=head1 Supported Platforms + +As of early March 2000 (the Perl release 5.6.0), the following +platforms are able to build Perl from the standard source code +distribution available at http://www.perl.com/CPAN/src/index.html + + AIX + DOS DJGPP 1) + EPOC + FreeBSD + HP-UX + IRIX + Linux + LynxOS + MachTen + MPE/iX + NetBSD + OpenBSD + OS/2 + QNX + Rhapsody/Darwin 2) + SCO SV + SINIX + Solaris + SVR4 + Tru64 UNIX 3) + UNICOS + UNICOS/mk + Unixware + VMS + VOS + Windows 3.1 1) + Windows 95 1) 4) + Windows 98 1) 4) + Windows NT 1) 4) + + 1) in DOS mode either the DOS or OS/2 ports can be used + 2) new in 5.6.0: the BSD/NeXT-based UNIX of Mac OS X + 3) formerly known as Digital UNIX and before that DEC OSF/1 + 4) compilers: Borland, Cygwin, Mingw32 EGCS/GCC, VC++ + +The following platforms worked for the previous major release +(5.005_03 being the latest maintenance release of that, as of early +March 2000), but be did not manage to test these in time for the 5.6.0 +release of Perl. There is a very good chance that these will work +just fine with 5.6.0. + + A/UX + BeOS + BSD/OS + DG/UX + DYNIX/ptx + DomainOS + Hurd + NextSTEP + OpenSTEP + PowerMAX + SCO ODT/OSR + SunOS + Ultrix + +The following platform worked for the previous major release (5.005_03 +being the latest maintenance release of that, as of early March 2000). +However, standardization on UTF-8 as the internal string representation +in 5.6.0 has introduced incompatibilities in this EBCDIC platform. +Support for this platform may be enabled in a future release: + + OS390 1) + + 1) Previously known as MVS, or OpenEdition MVS. + +Strongly related to the OS390 platform by also being EBCDIC-based +mainframe platforms are the following platforms: + + BS2000 + VM/ESA + +These are also not expected to work under 5.6.0 for the same reasons +as OS390. Contact the mailing list perl-mvs@perl.org for more details. + +MacOS (Classic, pre-X) is almost 5.6.0-ready; building from the source +does work with 5.6.0, but additional MacOS specific source code is needed +for a complete port. Contact the mailing list macperl-porters@macperl.org +for more information. + +The following platforms have been known to build Perl from source in +the past, but we haven't been able to verify their status for the +current release, either because the hardware/software platforms are +rare or because we don't have an active champion on these +platforms--or both: + + 3b1 + AmigaOS + ConvexOS + CX/UX + DC/OSx + DDE SMES + DOS EMX + Dynix + EP/IX + ESIX + FPS + GENIX + Greenhills + ISC + MachTen 68k + MiNT + MPC + NEWS-OS + Opus + Plan 9 + PowerUX + RISC/os + Stellar + SVR2 + TI1500 + TitanOS + Unisys Dynix + Unixware + +Support for the following platform is planned for a future Perl release: + + Netware + +The following platforms have their own source code distributions and +binaries available via http://www.perl.com/CPAN/ports/index.html: + + Perl release + + AS/400 5.003 + Netware 5.003_07 + Tandem Guardian 5.004 + +The following platforms have only binaries available via +http://www.perl.com/CPAN/ports/index.html : + + Perl release + + Acorn RISCOS 5.005_02 + AOS 5.002 + LynxOS 5.004_02 + +Although we do suggest that you always build your own Perl from +the source code, both for maximal configurability and for security, +in case you are in a hurry you can check +http://www.perl.com/CPAN/ports/index.html for binary distributions. + +=head1 SEE ALSO + +L, L, L, L, L, +L, L, L, L, L, +L, L, L, and L. + =head1 AUTHORS / CONTRIBUTORS -Abigail Eabigail@fnx.comE, -Charles Bailey Ebailey@newman.upenn.eduE, -Graham Barr Egbarr@pobox.comE, -Tom Christiansen Etchrist@perl.comE, -Nicholas Clark ENicholas.Clark@liverpool.ac.ukE, -Andy Dougherty Edoughera@lafcol.lafayette.eduE, -Dominic Dunlop Edomo@vo.luE, -Neale Ferguson Eneale@mailbox.tabnsw.com.auE -Paul Green EPaul_Green@stratus.comE, -M.J.T. Guy Emjtg@cus.cam.ac.ukE, -Jarkko Hietaniemi Ejhi@iki.fi, -Luther Huffman Elutherh@stratcom.comE, -Nick Ing-Simmons Enick@ni-s.u-net.comE, -Andreas J. KEnig Ekoenig@kulturbox.deE, -Markus Laker Emlaker@contax.co.ukE, -Andrew M. Langmead Eaml@world.std.comE, -Larry Moore Eljmoore@freespace.netE, -Paul Moore EPaul.Moore@uk.origin-it.comE, -Chris Nandor Epudge@pobox.comE, -Matthias Neeracher Eneeri@iis.ee.ethz.chE, -Gary Ng E71564.1743@CompuServe.COME, -Tom Phoenix Erootbeer@teleport.comE, -Peter Prymmer Epvhp@forte.comE, -Hugo van der Sanden Ehv@crypt0.demon.co.ukE, -Gurusamy Sarathy Egsar@umich.eduE, -Paul J. Schinder Eschinder@pobox.comE, -Michael G Schwern Eschwern@pobox.comE, -Dan Sugalski Esugalskd@ous.eduE, -Nathan Torkington Egnat@frii.comE. +Abigail , +Charles Bailey , +Graham Barr , +Tom Christiansen , +Nicholas Clark , +Thomas Dorner , +Andy Dougherty , +Dominic Dunlop , +Neale Ferguson , +David J. Fiander , +Paul Green , +M.J.T. Guy , +Jarkko Hietaniemi , +Luther Huffman , +Nick Ing-Simmons , +Andreas J. KEnig , +Markus Laker , +Andrew M. Langmead , +Larry Moore , +Paul Moore , +Chris Nandor , +Matthias Neeracher , +Gary Ng <71564.1743@CompuServe.COM>, +Tom Phoenix , +AndrE Pirard , +Peter Prymmer , +Hugo van der Sanden , +Gurusamy Sarathy , +Paul J. Schinder , +Michael G Schwern , +Dan Sugalski , +Nathan Torkington . This document is maintained by Chris Nandor -Epudge@pobox.comE. +. =head1 VERSION -Version 1.43, last modified 24 May 1999 +Version 1.47, last modified 22 March 2000