perlwin32.1

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

programs.  They consider it the application's job to handle that.
This is commonly achieved by linking the application (in our case,
perl) with startup code that the C runtime libraries usually provide.
However, doing that results in incompatible perl versions (since the
behavior of the argv expansion code differs depending on the
compiler, and it is even buggy on some compilers).  Besides, it may
be a source of frustration if you use such a perl binary with an
alternate shell that *does* expand wildcards.
.Sp
Instead, the following solution works rather well. The nice things
about it are 1) you can start using it right away; 2) it is more
powerful, because it will do the right thing with a pattern like
*/*/*.c; 3) you can decide whether you do/don't want to use it; and
4) you can extend the method to add any customizations (or even
entirely different kinds of wildcard expansion).
.Sp
.Vb 10
\&        C:\e> copy con c:\eperl\elib\eWild.pm
\&        # Wild.pm \- emulate shell @ARGV expansion on shells that don\*(Aqt
\&        use File::DosGlob;
\&        @ARGV = map {
\&                      my @g = File::DosGlob::glob($_) if /[*?]/;
\&                      @g ? @g : $_;
\&                    } @ARGV;
\&        1;
\&        ^Z
\&        C:\e> set PERL5OPT=\-MWild
\&        C:\e> perl \-le "for (@ARGV) { print }" */*/perl*.c
\&        p4view/perl/perl.c
\&        p4view/perl/perlio.c
\&        p4view/perl/perly.c
\&        perl5.005/win32/perlglob.c
\&        perl5.005/win32/perllib.c
\&        perl5.005/win32/perlglob.c
\&        perl5.005/win32/perllib.c
\&        perl5.005/win32/perlglob.c
\&        perl5.005/win32/perllib.c
.Ve
.Sp
Note there are two distinct steps there: 1) You'll have to create
Wild.pm and put it in your perl lib directory. 2) You'll need to
set the \s-1PERL5OPT\s0 environment variable.  If you want argv expansion
to be the default, just set \s-1PERL5OPT\s0 in your default startup
environment.
.Sp
If you are using the Visual C compiler, you can get the C runtime's
command line wildcard expansion built into perl binary.  The resulting
binary will always expand unquoted command lines, which may not be
what you want if you use a shell that does that for you.  The expansion
done is also somewhat less powerful than the approach suggested above.
.IP "Win32 Specific Extensions" 4
.IX Item "Win32 Specific Extensions"
A number of extensions specific to the Win32 platform are available
from \s-1CPAN\s0.  You may find that many of these extensions are meant to
be used under the Activeware port of Perl, which used to be the only
native port for the Win32 platform.  Since the Activeware port does not
have adequate support for Perl's extension building tools, these
extensions typically do not support those tools either and, therefore,
cannot be built using the generic steps shown in the previous section.
.Sp
To ensure smooth transitioning of existing code that uses the
ActiveState port, there is a bundle of Win32 extensions that contains
all of the ActiveState extensions and several other Win32 extensions from
\&\s-1CPAN\s0 in source form, along with many added bugfixes, and with MakeMaker
support.  The latest version of this bundle is available at:
.Sp
.Vb 1
\&    http://search.cpan.org/dist/libwin32/
.Ve
.Sp
See the \s-1README\s0 in that distribution for building and installation
instructions.
.IP "Notes on 64\-bit Windows" 4
.IX Item "Notes on 64-bit Windows"
Windows .NET Server supports the \s-1LLP64\s0 data model on the Intel Itanium
architecture.
.Sp
The \s-1LLP64\s0 data model is different from the \s-1LP64\s0 data model that is the
norm on 64\-bit Unix platforms.  In the former, \f(CW\*(C`int\*(C'\fR and \f(CW\*(C`long\*(C'\fR are
both 32\-bit data types, while pointers are 64 bits wide.  In addition,
there is a separate 64\-bit wide integral type, \f(CW\*(C`_\|_int64\*(C'\fR.  In contrast,
the \s-1LP64\s0 data model that is pervasive on Unix platforms provides \f(CW\*(C`int\*(C'\fR
as the 32\-bit type, while both the \f(CW\*(C`long\*(C'\fR type and pointers are of
64\-bit precision.  Note that both models provide for 64\-bits of
addressability.
.Sp
64\-bit Windows running on Itanium is capable of running 32\-bit x86
binaries transparently.  This means that you could use a 32\-bit build
of Perl on a 64\-bit system.  Given this, why would one want to build
a 64\-bit build of Perl?  Here are some reasons why you would bother:
.RS 4
.IP "\(bu" 4
A 64\-bit native application will run much more efficiently on
Itanium hardware.
.IP "\(bu" 4
There is no 2GB limit on process size.
.IP "\(bu" 4
Perl automatically provides large file support when built under
64\-bit Windows.
.IP "\(bu" 4
Embedding Perl inside a 64\-bit application.
.RE
.RS 4
.RE
.Sh "Running Perl Scripts"
.IX Subsection "Running Perl Scripts"
Perl scripts on \s-1UNIX\s0 use the \*(L"#!\*(R" (a.k.a \*(L"shebang\*(R") line to
indicate to the \s-1OS\s0 that it should execute the file using perl.
Win32 has no comparable means to indicate arbitrary files are
executables.
.PP
Instead, all available methods to execute plain text files on
Win32 rely on the file \*(L"extension\*(R".  There are three methods
to use this to execute perl scripts:
.IP "1." 8
There is a facility called \*(L"file extension associations\*(R" that will
work in Windows \s-1NT\s0 4.0.  This can be manipulated via the two
commands \*(L"assoc\*(R" and \*(L"ftype\*(R" that come standard with Windows \s-1NT\s0
4.0.  Type \*(L"ftype /?\*(R" for a complete example of how to set this
up for perl scripts (Say what?  You thought Windows \s-1NT\s0 wasn't
perl-ready? :).
.IP "2." 8
Since file associations don't work everywhere, and there are
reportedly bugs with file associations where it does work, the
old method of wrapping the perl script to make it look like a
regular batch file to the \s-1OS\s0, may be used.  The install process
makes available the \*(L"pl2bat.bat\*(R" script which can be used to wrap
perl scripts into batch files.  For example:
.Sp
.Vb 1
\&        pl2bat foo.pl
.Ve
.Sp
will create the file \*(L"\s-1FOO\s0.BAT\*(R".  Note \*(L"pl2bat\*(R" strips any
\&.pl suffix and adds a .bat suffix to the generated file.
.Sp
If you use the 4DOS/NT or similar command shell, note that
\&\*(L"pl2bat\*(R" uses the \*(L"%*\*(R" variable in the generated batch file to
refer to all the command line arguments, so you may need to make
sure that construct works in batch files.  As of this writing,
4DOS/NT users will need a \*(L"ParameterChar = *\*(R" statement in their
4NT.INI file or will need to execute \*(L"setdos /p*\*(R" in the 4DOS/NT
startup file to enable this to work.
.IP "3." 8
Using \*(L"pl2bat\*(R" has a few problems:  the file name gets changed,
so scripts that rely on \f(CW$0\fR to find what they must do may not
run properly; running \*(L"pl2bat\*(R" replicates the contents of the
original script, and so this process can be maintenance intensive
if the originals get updated often.  A different approach that
avoids both problems is possible.
.Sp
A script called \*(L"runperl.bat\*(R" is available that can be copied
to any filename (along with the .bat suffix).  For example,
if you call it \*(L"foo.bat\*(R", it will run the file \*(L"foo\*(R" when it is
executed.  Since you can run batch files on Win32 platforms simply
by typing the name (without the extension), this effectively
runs the file \*(L"foo\*(R", when you type either \*(L"foo\*(R" or \*(L"foo.bat\*(R".
With this method, \*(L"foo.bat\*(R" can even be in a different location
than the file \*(L"foo\*(R", as long as \*(L"foo\*(R" is available somewhere on
the \s-1PATH\s0.  If your scripts are on a filesystem that allows symbolic
links, you can even avoid copying \*(L"runperl.bat\*(R".
.Sp
Here's a diversion:  copy \*(L"runperl.bat\*(R" to \*(L"runperl\*(R", and type
\&\*(L"runperl\*(R".  Explain the observed behavior, or lack thereof. :)
Hint: .gnidnats llits er'uoy fi ,\*(L"lrepnur\*(R" eteled :tniH
.Sh "Miscellaneous Things"
.IX Subsection "Miscellaneous Things"
A full set of \s-1HTML\s0 documentation is installed, so you should be
able to use it if you have a web browser installed on your
system.
.PP
\&\f(CW\*(C`perldoc\*(C'\fR is also a useful tool for browsing information contained
in the documentation, especially in conjunction with a pager
like \f(CW\*(C`less\*(C'\fR (recent versions of which have Win32 support).  You may
have to set the \s-1PAGER\s0 environment variable to use a specific pager.
\&\*(L"perldoc \-f foo\*(R" will print information about the perl operator
\&\*(L"foo\*(R".
.PP
One common mistake when using this port with a \s-1GUI\s0 library like \f(CW\*(C`Tk\*(C'\fR
is assuming that Perl's normal behavior of opening a command-line
window will go away.  This isn't the case.  If you want to start a copy
of \f(CW\*(C`perl\*(C'\fR without opening a command-line window, use the \f(CW\*(C`wperl\*(C'\fR
executable built during the installation process.  Usage is exactly
the same as normal \f(CW\*(C`perl\*(C'\fR on Win32, except that options like \f(CW\*(C`\-h\*(C'\fR
don't work (since they need a command-line window to print to).
.PP
If you find bugs in perl, you can run \f(CW\*(C`perlbug\*(C'\fR to create a
bug report (you may have to send it manually if \f(CW\*(C`perlbug\*(C'\fR cannot
find a mailer on your system).
.SH "BUGS AND CAVEATS"
.IX Header "BUGS AND CAVEATS"
Norton AntiVirus interferes with the build process, particularly if
set to \*(L"AutoProtect, All Files, when Opened\*(R". Unlike large applications
the perl build process opens and modifies a lot of files. Having the
the AntiVirus scan each and every one slows build the process significantly.
Worse, with PERLIO=stdio the build process fails with peculiar messages
as the virus checker interacts badly with miniperl.exe writing configure
files (it seems to either catch file part written and treat it as suspicious,
or virus checker may have it \*(L"locked\*(R" in a way which inhibits miniperl
updating it). The build does complete with
.PP
.Vb 1
\&   set PERLIO=perlio
.Ve
.PP
but that may be just luck. Other AntiVirus software may have similar issues.
.PP
Some of the built-in functions do not act exactly as documented in
perlfunc, and a few are not implemented at all.  To avoid
surprises, particularly if you have had prior exposure to Perl
in other operating environments or if you intend to write code
that will be portable to other environments, see perlport
for a reasonably definitive list of these differences.
.PP
Not all extensions available from \s-1CPAN\s0 may build or work properly
in the Win32 environment.  See \*(L"Building Extensions\*(R".
.PP
Most \f(CW\*(C`socket()\*(C'\fR related calls are supported, but they may not
behave as on Unix platforms.  See perlport for the full list.
Perl requires Winsock2 to be installed on the system. If you're
running Win95, you can download Winsock upgrade from here:
.PP
http://www.microsoft.com/windows95/downloads/contents/WUAdminTools/S_WUNetworkingTools/W95Sockets2/Default.asp
.PP
Later \s-1OS\s0 versions already include Winsock2 support.
.PP
Signal handling may not behave as on Unix platforms (where it
doesn't exactly \*(L"behave\*(R", either :).  For instance, calling \f(CW\*(C`die()\*(C'\fR
or \f(CW\*(C`exit()\*(C'\fR from signal handlers will cause an exception, since most
implementations of \f(CW\*(C`signal()\*(C'\fR on Win32 are severely crippled.
Thus, signals may work only for simple things like setting a flag
variable in the handler.  Using signals under this port should
currently be considered unsupported.
.PP
Please send detailed descriptions of any problems and solutions that
you may find to <\[e-mail]\fR>, along with the output
produced by \f(CW\*(C`perl \-V\*(C'\fR.
.SH "ACKNOWLEDGEMENTS"
.IX Header "ACKNOWLEDGEMENTS"
The use of a camel with the topic of Perl is a trademark
of O'Reilly and Associates, Inc. Used with permission.
.SH "AUTHORS"
.IX Header "AUTHORS"
.IP "Gary Ng <[e-mail]>" 4
.IX Item "Gary Ng <[e-mail]>"
.PD 0
.IP "Gurusamy Sarathy <[e-mail]>" 4
.IX Item "Gurusamy Sarathy <[e-mail]>"
.IP "Nick Ing-Simmons <nick@ing\-simmons.net>" 4
.IX Item "Nick Ing-Simmons <[e-mail]>"
.IP "Jan Dubois <[e-mail]>" 4
.IX Item "Jan Dubois <[e-mail]>"
.IP "Steve Hay <[e-mail]>" 4
.IX Item "Steve Hay <[e-mail]>"
.PD
.PP
This document is maintained by Jan Dubois.
.SH "SEE ALSO"
.IX Header "SEE ALSO"
perl
.SH "HISTORY"
.IX Header "HISTORY"
This port was originally contributed by Gary Ng around 5.003_24,
and borrowed from the Hip Communications port that was available
at the time.  Various people have made numerous and sundry hacks
since then.
.PP
Borland support was added in 5.004_01 (Gurusamy Sarathy).
.PP
GCC/mingw32 support was added in 5.005 (Nick Ing-Simmons).
.PP
Support for \s-1PERL_OBJECT\s0 was added in 5.005 (ActiveState Tool Corp).
.PP
Support for \fIfork()\fR emulation was added in 5.6 (ActiveState Tool Corp).
.PP
Win9x support was added in 5.6 (Benjamin Stuhl).
.PP
Support for 64\-bit Windows added in 5.8 (ActiveState Corp).
.PP
Last updated: 29 August 2007