perl572delta.1

视频监控网络部分的协议ddns,的模块的实现代码,请大家大胆指正.

to be closer to the library/extension they are testing.)
.SH "Known Problems"
.IX Header "Known Problems"
Note that unlike other sections in this document (which describe
changes since 5.7.0) this section is cumulative containing known
problems for all the 5.7 releases.
.Sh "\s-1AIX\s0"
.IX Subsection "AIX"
.IP "\(bu" 4
In \s-1AIX\s0 4.2 Perl extensions that use \*(C+ functions that use statics
may have problems in that the statics are not getting initialized.
In newer \s-1AIX\s0 releases this has been solved by linking Perl with
the libC_r library, but unfortunately in \s-1AIX\s0 4.2 the said library
has an obscure bug where the various functions related to time
(such as \fItime()\fR and \fIgettimeofday()\fR) return broken values, and
therefore in \s-1AIX\s0 4.2 Perl is not linked against the libC_r.
.IP "\(bu" 4
vac 5.0.0.0 May Produce Buggy Code For Perl
.Sp
The \s-1AIX\s0 C compiler vac version 5.0.0.0 may produce buggy code,
resulting in few random tests failing, but when the failing tests
are run by hand, they succeed.  We suggest upgrading to at least
vac version 5.0.1.0, that has been known to compile Perl correctly.
\&\*(L"lslpp \-L|grep vac.C\*(R" will tell you the vac version.
.Sh "Amiga Perl Invoking Mystery"
.IX Subsection "Amiga Perl Invoking Mystery"
One cannot call Perl using the \f(CW\*(C`volume:\*(C'\fR syntax, that is, \f(CW\*(C`perl \-v\*(C'\fR
works, but for example \f(CW\*(C`bin:perl \-v\*(C'\fR doesn't.  The exact reason is
known but the current suspect is the \fIixemul\fR library.
.Sh "lib/ftmp\-security tests warn 'system possibly insecure'"
.IX Subsection "lib/ftmp-security tests warn 'system possibly insecure'"
Don't panic.  Read \s-1INSTALL\s0 'make test' section instead.
.Sh "Cygwin intermittent failures of lib/Memoize/t/expire_file 11 and 12"
.IX Subsection "Cygwin intermittent failures of lib/Memoize/t/expire_file 11 and 12"
The subtests 11 and 12 sometimes fail and sometimes work.
.Sh "HP-UX lib/io_multihomed Fails When LP64\-Configured"
.IX Subsection "HP-UX lib/io_multihomed Fails When LP64-Configured"
The lib/io_multihomed test may hang in HP-UX if Perl has been
configured to be 64\-bit. Because other 64\-bit platforms do not hang in
this test, HP-UX is suspect. All other tests pass in 64\-bit HP-UX. The
test attempts to create and connect to \*(L"multihomed\*(R" sockets (sockets
which have multiple \s-1IP\s0 addresses).
.Sh "HP-UX lib/posix Subtest 9 Fails When LP64\-Configured"
.IX Subsection "HP-UX lib/posix Subtest 9 Fails When LP64-Configured"
If perl is configured with \-Duse64bitall, the successful result of the
subtest 10 of lib/posix may arrive before the successful result of the
subtest 9, which confuses the test harness so much that it thinks the
subtest 9 failed.
.Sh "Linux With Sfio Fails op/misc Test 48"
.IX Subsection "Linux With Sfio Fails op/misc Test 48"
No known fix.
.Sh "\s-1OS/390\s0"
.IX Subsection "OS/390"
\&\s-1OS/390\s0 has rather many test failures but the situation is actually
better than it was in 5.6.0, it's just that so many new modules and
tests have been added.
.PP
.Vb 10
\& Failed Test                     Stat Wstat Total Fail  Failed  List of Failed
\& \-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-
\& ../ext/B/Deparse.t                            14    1   7.14%  14
\& ../ext/B/Showlex.t                             1    1 100.00%  1
\& ../ext/Encode/Encode/Tcl.t                   610   13   2.13%  592 594 596 598
\&                                                                600 602 604\-610
\& ../ext/IO/lib/IO/t/io_unix.t     113 28928     5    3  60.00%  3\-5
\& ../ext/POSIX/POSIX.t                          29    1   3.45%  14
\& ../ext/Storable/t/lock.t         255 65280     5    3  60.00%  3\-5
\& ../lib/locale.t                  129 33024   117   19  16.24%  99\-117
\& ../lib/warnings.t                            434    1   0.23%  75
\& ../lib/ExtUtils.t                             27    1   3.70%  25
\& ../lib/Math/BigInt/t/bigintpm.t             1190    1   0.08%  1145
\& ../lib/Unicode/UCD.t                          81   48  59.26%  1\-16 49\-64 66\-81
\& ../lib/User/pwent.t                            9    1  11.11%  4
\& op/pat.t                                     660    6   0.91%  242\-243 424\-425
\&                                                                626\-627
\& op/split.t                         0     9    ??   ??       %  ??
\& op/taint.t                                   174    3   1.72%  156 162 168
\& op/tr.t                                       70    3   4.29%  50 58\-59
\& Failed 16/422 test scripts, 96.21% okay. 105/23251 subtests failed, 99.55% okay.
.Ve
.Sh "op/sprintf tests 129 and 130"
.IX Subsection "op/sprintf tests 129 and 130"
The op/sprintf tests 129 and 130 are known to fail on some platforms.
Examples include any platform using sfio, and Compaq/Tandem's NonStop-UX.
The failing platforms do not comply with the \s-1ANSI\s0 C Standard, line
19ff on page 134 of \s-1ANSI\s0 X3.159 1989 to be exact.  (They produce
something other than \*(L"1\*(R" and \*(L"\-1\*(R" when formatting 0.6 and \-0.6 using
the printf format \*(L"%.0f\*(R", most often they produce \*(L"0\*(R" and \*(L"\-0\*(R".)
.Sh "Failure of Thread tests"
.IX Subsection "Failure of Thread tests"
\&\fBNote that support for 5.005\-style threading remains experimental.\fR
.PP
The following tests are known to fail due to fundamental problems in
the 5.005 threading implementation. These are not new failures\*(--Perl
5.005_0x has the same bugs, but didn't have these tests.
.PP
.Vb 2
\&  lib/autouse.t                 4
\&  t/lib/thr5005.t               19\-20
.Ve
.Sh "\s-1UNICOS\s0"
.IX Subsection "UNICOS"
.IP "\(bu" 4
ext/POSIX/sigaction subtests 6 and 13 may fail.
.IP "\(bu" 4
lib/ExtUtils may spuriously claim that subtest 28 failed,
which is interesting since the test only has 27 tests.
.IP "\(bu" 4
Numerous numerical test failures
.Sp
.Vb 5
\&  op/numconvert                 209,210,217,218
\&  op/override                   7
\&  ext/Time/HiRes/HiRes          9
\&  lib/Math/BigInt/t/bigintpm    1145
\&  lib/Math/Trig                 25
.Ve
.Sp
These tests fail because of yet unresolved floating point inaccuracies.
.Sh "\s-1UTS\s0"
.IX Subsection "UTS"
There are a few known test failures, see perluts.
.Sh "\s-1VMS\s0"
.IX Subsection "VMS"
Rather many tests are failing in \s-1VMS\s0 but that actually more tests
succeed in \s-1VMS\s0 than they used to, it's just that there are many,
many more tests than there used to be.
.PP
Here are the known failures from some compiler/platform combinations.
.PP
\&\s-1DEC\s0 C V5.3\-006 on OpenVMS \s-1VAX\s0 V6.2
.PP
.Vb 9
\&  [\-.ext.list.util.t]tainted..............FAILED on test 3
\&  [\-.ext.posix]sigaction..................FAILED on test 7
\&  [\-.ext.time.hires]hires.................FAILED on test 14
\&  [\-.lib.file.find]taint..................FAILED on test 17
\&  [\-.lib.math.bigint.t]bigintpm...........FAILED on test 1183
\&  [\-.lib.test.simple.t]exit...............FAILED on test 1
\&  [.lib]vmsish............................FAILED on test 13
\&  [.op]sprintf............................FAILED on test 12
\&  Failed 8/399 tests, 91.23% okay.
.Ve
.PP
\&\s-1DEC\s0 C V6.0\-001 on OpenVMS Alpha V7.2\-1 and
Compaq C V6.2\-008 on OpenVMS Alpha V7.1
.PP
.Vb 5
\&  [\-.ext.list.util.t]tainted..............FAILED on test 3 
\&  [\-.lib.file.find]taint..................FAILED on test 17
\&  [\-.lib.test.simple.t]exit...............FAILED on test 1
\&  [.lib]vmsish............................FAILED on test 13
\&  Failed 4/399 tests, 92.48% okay.
.Ve
.PP
Compaq C V6.4\-005 on OpenVMS Alpha 7.2.1
.PP
.Vb 7
\&  [\-.ext.b]showlex........................FAILED on test 1
\&  [\-.ext.list.util.t]tainted..............FAILED on test 3
\&  [\-.lib.file.find]taint..................FAILED on test 17 
\&  [\-.lib.test.simple.t]exit...............FAILED on test 1
\&  [.lib]vmsish............................FAILED on test 13
\&  [.op]misc...............................FAILED on test 49
\&  Failed 6/401 tests, 92.77% okay.
.Ve
.Sh "Win32"
.IX Subsection "Win32"
In multi-CPU boxes there are some problems with the I/O buffering:
some output may appear twice.
.Sh "Localising a Tied Variable Leaks Memory"
.IX Subsection "Localising a Tied Variable Leaks Memory"
.Vb 2
\&    use Tie::Hash;
\&    tie my %tie_hash => \*(AqTie::StdHash\*(Aq;
\&
\&    ...
\&
\&    local($tie_hash{Foo}) = 1; # leaks
.Ve
.PP
Code like the above is known to leak memory every time the \fIlocal()\fR
is executed.
.Sh "Self-tying of Arrays and Hashes Is Forbidden"
.IX Subsection "Self-tying of Arrays and Hashes Is Forbidden"
Self-tying of arrays and hashes is broken in rather deep and
hard-to-fix ways.  As a stop-gap measure to avoid people from getting
frustrated at the mysterious results (core dumps, most often) it is
for now forbidden (you will get a fatal error even from an attempt).
.Sh "Variable Attributes are not Currently Usable for Tieing"
.IX Subsection "Variable Attributes are not Currently Usable for Tieing"
This limitation will hopefully be fixed in future.  (Subroutine
attributes work fine for tieing, see Attribute::Handlers).
.Sh "Building Extensions Can Fail Because Of Largefiles"
.IX Subsection "Building Extensions Can Fail Because Of Largefiles"
Some extensions like mod_perl are known to have issues with
`largefiles', a change brought by Perl 5.6.0 in which file offsets
default to 64 bits wide, where supported.  Modules may fail to compile
at all or compile and work incorrectly.  Currently there is no good
solution for the problem, but Configure now provides appropriate
non-largefile ccflags, ldflags, libswanted, and libs in the \f(CW%Config\fR
hash (e.g., \f(CW$Config\fR{ccflags_nolargefiles}) so the extensions that are
having problems can try configuring themselves without the
largefileness.  This is admittedly not a clean solution, and the
solution may not even work at all.  One potential failure is whether
one can (or, if one can, whether it's a good idea) link together at
all binaries with different ideas about file offsets, all this is
platform-dependent.
.Sh "The Compiler Suite Is Still Experimental"
.IX Subsection "The Compiler Suite Is Still Experimental"
The compiler suite is slowly getting better but is nowhere near
working order yet.
.Sh "The Long Double Support is Still Experimental"
.IX Subsection "The Long Double Support is Still Experimental"
The ability to configure Perl's numbers to use \*(L"long doubles\*(R",
floating point numbers of hopefully better accuracy, is still
experimental.  The implementations of long doubles are not yet
widespread and the existing implementations are not quite mature
or standardised, therefore trying to support them is a rare
and moving target.  The gain of more precision may also be offset
by slowdown in computations (more bits to move around, and the
operations are more likely to be executed by less optimised
libraries).
.SH "Reporting Bugs"
.IX Header "Reporting Bugs"
If you find what you think is a bug, you might check the articles
recently posted to the comp.lang.perl.misc newsgroup and the perl
bug database at http://bugs.perl.org/  There may also be
information at http://www.perl.com/perl/ , the Perl Home Page.
.PP
If you believe you have an unreported bug, please run the \fBperlbug\fR
program included with your release.  Be sure to trim your bug down
to a tiny but sufficient test case.  Your bug report, along with the
output of \f(CW\*(C`perl \-V\*(C'\fR, will be sent off to [e-mail] to be
analysed by the Perl porting team.
.SH "SEE ALSO"
.IX Header "SEE ALSO"
The \fIChanges\fR file for exhaustive details on what changed.
.PP
The \fI\s-1INSTALL\s0\fR file for how to build Perl.
.PP
The \fI\s-1README\s0\fR file for general stuff.
.PP
The \fIArtistic\fR and \fICopying\fR files for copyright information.
.SH "HISTORY"
.IX Header "HISTORY"
Written by Jarkko Hietaniemi <\[e-mail]\fR>, with many contributions
from The Perl Porters and Perl Users submitting feedback and patches.
.PP
Send omissions or corrections to <\[e-mail]\fR>.