X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=blobdiff_plain;f=pod%2Fperlport.pod;h=70b95b05ab57ad6a4bc22530c7b6b6faa9208f16;hb=b1866b2db57c4aa1ee77325f2658722f6a7befa2;hp=7f779c955e9816ca3b3af5fcc09c2264a5b9dd07;hpb=4375e838ae24b385ae79fa7b6918e613bedaaee6;p=p5sagit%2Fp5-mst-13.2.git diff --git a/pod/perlport.pod b/pod/perlport.pod index 7f779c9..70b95b0 100644 --- a/pod/perlport.pod +++ b/pod/perlport.pod @@ -181,10 +181,12 @@ 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, VAX) 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. +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: @@ -681,7 +683,7 @@ The ActiveState Pages, http://www.activestate.com/ =item * The Cygwin environment for Win32; F (installed -as L), http://sourceware.cygnus.com/cygwin/ +as L), http://sources.redhat.com/cygwin/ =item * @@ -1042,7 +1044,8 @@ Also see: * -L, F, F, F +L, F, F, F, +L. =item * @@ -1053,7 +1056,7 @@ general usage issues for all EBCDIC Perls. Send a message body of =item * AS/400 Perl information at -ttp://as400.rochester.ibm.com/ +http://as400.rochester.ibm.com/ as well as on CPAN in the F directory. =back @@ -1640,6 +1643,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) @@ -1650,6 +1657,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) @@ -1746,7 +1756,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)