diff options
Diffstat (limited to 'Master/tlpkg/tlperl/lib/pods/perlport.pod')
-rw-r--r-- | Master/tlpkg/tlperl/lib/pods/perlport.pod | 15 |
1 files changed, 6 insertions, 9 deletions
diff --git a/Master/tlpkg/tlperl/lib/pods/perlport.pod b/Master/tlpkg/tlperl/lib/pods/perlport.pod index 0193dc852ca..867b66e2915 100644 --- a/Master/tlpkg/tlperl/lib/pods/perlport.pod +++ b/Master/tlpkg/tlperl/lib/pods/perlport.pod @@ -622,7 +622,7 @@ format. Don't assume that the epoch starts at 00:00:00, January 1, 1970, because that is OS- and implementation-specific. It is better to store a date in an unambiguous representation. The ISO 8601 standard -defines YYYY-MM-DD as the date format, or YYYY-MM-DDTHH-MM-SS +defines YYYY-MM-DD as the date format, or YYYY-MM-DDTHH:MM:SS (that's a literal "T" separating the date from the time). Please do use the ISO 8601 instead of making us guess what date 02/03/04 might be. ISO 8601 even sorts nicely as-is. @@ -689,10 +689,6 @@ If your code is destined for systems with severely constrained (or missing!) virtual memory systems then you want to be I<especially> mindful of avoiding wasteful constructs such as: - # NOTE: this is no longer "bad" in perl5.005 - for (0..10000000) {} # bad - for (my $x = 0; $x <= 10000000; ++$x) {} # good - my @lines = <$very_large_file>; # bad while (<$fh>) {$file .= $_} # sometimes bad @@ -904,6 +900,8 @@ DOSish perls are as follows: Windows Vista MSWin32 MSWin32-x86 2 6 00 Windows 7 MSWin32 MSWin32-x86 2 6 01 Windows 7 MSWin32 MSWin32-x64 2 6 01 + Windows 2008 MSWin32 MSWin32-x86 2 6 01 + Windows 2008 MSWin32 MSWin32-x64 2 6 01 Windows CE MSWin32 ? 3 Cygwin cygwin cygwin @@ -1394,8 +1392,8 @@ subdirectories named after the suffix. Hence files are translated: The Unix emulation library's translation of filenames to native assumes that this sort of translation is required, and it allows a user-defined list of known suffixes that it will transpose in this fashion. This may -seem transparent, but consider that with these rules C<foo/bar/baz.h> -and C<foo/bar/h/baz> both map to C<foo.bar.h.baz>, and that C<readdir> and +seem transparent, but consider that with these rules F<foo/bar/baz.h> +and F<foo/bar/h/baz> both map to F<foo.bar.h.baz>, and that C<readdir> and C<glob> cannot and do not attempt to emulate the reverse mapping. Other C<.>'s in filenames are translated to C</>. @@ -2141,7 +2139,6 @@ Caveats: =back - =item Symbian (Series 60 v3, 3.2 and 5 - what else?) =item Stratus VOS / OpenVOS @@ -2315,7 +2312,7 @@ L<http://www.cpan.org/ports/index.html> for binary distributions. =head1 SEE ALSO -L<perlaix>, L<perlamiga>, L<perlapollo>, L<perlbeos>, L<perlbs2000>, +L<perlaix>, L<perlamiga>, L<perlbeos>, L<perlbs2000>, L<perlce>, L<perlcygwin>, L<perldgux>, L<perldos>, L<perlepoc>, L<perlebcdic>, L<perlfreebsd>, L<perlhurd>, L<perlhpux>, L<perlirix>, L<perlmacos>, L<perlmacosx>, L<perlmpeix>, |