flock( ) - Githubissues

Migrated from rt.perl.org#2357 (status was 'resolved')

Searchable as RT2357$

From ratsim@yahoo.fr

Created by ratsim@yahoo.fr

I use Apache Web Server 1.3.9 on Windows 98 and in the error.log I can read this:

[Mon Mar 13 14:10:32 2000] [error] [client 192.168.1.3] Premature end of script headers: c:/program files/apache group/apache/cgi-bin/acctman.pl [Mon Mar 13 14:10:32 2000] [error] [client 192.168.1.3] flock() unimplemented on this platform at c:/program files/apache group/apache/cgi-bin/acctman.pl line 672

I'm not programmer but if you can help me\, it's good Thank you

Perl Info

``` Site configuration information for perl 5.00503: Summary of my perl5 (5.0 patchlevel 5 subversion 03) configuration: Platform: osname=MSWin32, osvers=4.0, archname=MSWin32-x86-object uname='' hint=recommended, useposix=true, d_sigaction=undef usethreads=undef useperlio=undef d_sfio=undef Compiler: cc='cl.exe', optimize='-Od -MD -DNDEBUG -TP -GX', gccversion= cppflags='-DWIN32' ccflags ='-Od -MD -DNDEBUG -TP -GX -DWIN32 -D_CONSOLE -DNO_STRICT -DHAVE_DES_FCRYPT -DPERL_OBJECT' stdchar='char', d_stdstdio=define, usevfork=false intsize=4, longsize=4, ptrsize=4, doublesize=8 d_longlong=undef, longlongsize=8, d_longdbl=define, longdblsize=10 alignbytes=8, usemymalloc=n, prototype=define Linker and Libraries: ld='link', ldflags ='-nologo -nodefaultlib -release -libpath:"c:\windows\Perl\lib\CORE" -machine:x86' libpth="c:\windows\Perl\lib\CORE" libs= oldnames.lib kernel32.lib user32.lib gdi32.lib winspool.lib comdlg32.lib advapi32.lib shell32.lib ole32.lib oleaut32.lib netapi32.lib uuid.lib wsock32.lib mpr.lib winmm.lib version.lib odbc32.lib odbccp32.lib PerlCRT.lib libc=c:\windows\Perl\lib\CORE\PerlCRT.lib, so=dll, useshrplib=yes, libperl=perlcore.lib Dynamic Linking: dlsrc=dl_win32.xs, dlext=dll, d_dlsymun=undef, ccdlflags=' ' cccdlflags=' ', lddlflags='-dll -nologo -nodefaultlib -release -libpath:"c:\windows\Perl\lib\CORE" -machine:x86' Locally applied patches: ACTIVEPERL_LOCAL_PATCHES_ENTRY @INC for perl 5.00503: C:/WINDOWS/Perl/lib C:/WINDOWS/Perl/site/lib . Environment for perl 5.00503: HOME (unset) LANG (unset) LANGUAGE (unset) LD_LIBRARY_PATH (unset) LOGDIR (unset) PATH=C:\WINDOWS;c:\windows;c:\windows\COMMAND PERL_BADLANG (unset) SHELL (unset) ___________________________________________________________ Do You Yahoo!? Achetez, vendez! À votre prix! Sur http://encheres.yahoo.fr ```

From [Unknown Contact. See original ticket]

At 12:49 +0100 2000-03-13\, RATSIMANDRESY Arison wrote:

flock() unimplemented on this platform at c:/program files/apache group/apache/cgi-bin/acctman.pl line 672

...

Summary of my perl5 (5.0 patchlevel 5 subversion 03) configuration: Platform: osname=MSWin32\, osvers=4.0\,

flock() is an advisory file-locking mechanism which allows cooperating programs to share files without fighting over them. The file README.win32 distributed with perl 5.005_03 (and the forthcoming 5.6.0) says

* The following functions are currently unavailable: `fork()'\, `dump()'\, `chown()'\, `link()'\, `symlink()'\, `chroot()'\, `setpgrp()' and related security functions\, `setpriority()'\, `getpriority()'\, `syscall()'\, `fcntl()'\, `getpw*()'\, `msg*()'\, `shm*()'\, `sem*()'\, `alarm()'\, `socketpair()'\, `*netent()'\, `*protoent()'\, `*servent()'\, `*hostent()'\, `getnetby*()'. This list is possibly incomplete.

I don't know whether flock() should be a member of that list or not. Can somebody who knows more about Perl on Windows help\, please?

Whether or not Perl's documentation needs updating\, Arison\, you may get more immediate help by taking the query to the newsgroup news:comp.infosystems.www.authoring.cgi. Good luck. -- Dominic Dunlop

From @gsar

On Mon\, 13 Mar 2000 14:53:30 +0100\, Dominic Dunlop wrote:

flock() is an advisory file-locking mechanism which allows cooperating programs to share files without fighting over them. The file README.win32 distributed with perl 5.005_03 (and the forthcoming 5.6.0) says
\*       The following functions are currently unavailable&#8203;: \`fork'\,
        \`dump'\, \`chown'\, \`link'\, \`symlink'\, \`chroot'\,
        \`setpgrp' and related security functions\, \`setpriority'\,
        \`getpriority'\, \`syscall'\, \`fcntl'\, \`getpw\*'\, \`msg\*'\,
        \`shm\*'\, \`sem\*'\, \`alarm'\, \`socketpair'\, \`\*netent'\,
        \`\*protoent'\, \`\*servent'\, \`\*hostent'\, \`getnetby\*'\. This
        list is possibly incomplete\.
I don't know whether flock() should be a member of that list or not. Can somebody who knows more about Perl on Windows help\, please?

That list from README.win32/perlwin32.pod should be removed--the canonical list can be found in perlport.pod (which is far more useful for comparing portability\, since it includes all other systems as well).

Sarathy gsar@ActiveState.com

From [Unknown Contact. See original ticket]

At 09:37 -0800 2000-03-13\, Gurusamy Sarathy wrote:

That list from README.win32/perlwin32.pod should be removed--the canonical list can be found in perlport.pod (which is far more useful for comparing portability\, since it includes all other systems as well).

Well\, perlport suggests that README.win32 is (more) definitive:

The list may well be incomplete\, or even wrong in some places. When in doubt\, consult the platform-specific README files in the Perl source distribution\, and any other documentation resources accompanying a given port.

However\, at the risk of sending people round in circles\, I append a patch (^Ms lost). I've taken the opportunity to update web links (on the assumption that www.cpan.org is now the official starting point for CPAN access)\, but don't have a replacement for the now-dead ftp://fractal.mta.ca/pub/crypto/SSLeay/DES/.

There's more work to be done by somebody who knows more about the port than I do. For example\, there's no mention whatever in the README of Windows 98\, never mind 2000; and the notes on globbing need attention now that perl does it without an external helper. (This is true of perlport.pod as well.)

Anyway\, that patch:

Inline Patch

```diff --- perl-5.6.0-RC1/README.win32~ Thu Mar 9 18:53:14 2000 +++ perl-5.6.0-RC1/README.win32 Tue Mar 14 10:53:18 2000 @@ -90,7 +90,7 @@ A port of dmake for win32 platforms is available from: - http://cpan.perl.org/authors/id/GSAR/dmake-4.1pl1-win32.zip + http://www.cpan.org/authors/Gurusamy_Sarathy/dmake-4.1pl1-win32.zip (This is a fixed version of original dmake sources obtained from http://www.wticorp.com/dmake/. As of version 4.1PL1, the original @@ -382,7 +382,12 @@ The Comprehensive Perl Archive Network (CPAN) offers a wealth of extensions, some of which require a C compiler to build. -Look in http://www.perl.com/ for more information on CPAN. +Look in http://www.cpan.org/ for more information on CPAN. + +Note that not all of the extensions available from CPAN are known or +intended to work in the Win32 environment: you should check the +information at http://testers.cpan.org/ before investing too much +effort in downloading and building any module. Most extensions (whether they require a C compiler or not) can be built, tested and installed with the standard mantra: @@ -407,7 +412,7 @@ Another option is to use the make written in Perl, available from CPAN: - http://www.perl.com/CPAN/authors/id/NI-S/Make-0.03.tar.gz + http://www.cpan.org/authors/Nick_Ing-Simmons/Make-1.00.tar.gz You may also use dmake. See L above on how to get it. @@ -500,9 +505,10 @@ ActiveState port, there is a bundle of Win32 extensions that contains all of the ActiveState extensions and most other Win32 extensions from CPAN in source form, along with many added bugfixes, and with MakeMaker -support. This bundle is available at: +support. The current release of this bundle at the time of writing +is available as: - http://www.perl.com/CPAN/authors/id/GSAR/libwin32-0.14.zip + http://www.cpan.org/authors/Gurusamy_Sarathy/libwin32-0.151.zip See the README in that distribution for building and installation instructions. Look for later versions that may be available at the @@ -609,99 +615,23 @@ the functions in this layer, thereby ensuring that both perl and extensions use the same runtime functions. -If you have had prior exposure to Perl on Unix platforms, you will notice -this port exhibits behavior different from what is documented. Most of the -differences fall under one of these categories. We do not consider -any of them to be serious limitations (especially when compared to the -limited nature of some of the Win32 OSes themselves :) - -=over 8 - -=item * - -C and C functions may not behave as documented. They -may return values that bear no resemblance to those reported on Unix -platforms, and some fields (like the the one for inode) may be completely -bogus. - -=item * - -The following functions are currently unavailable: C, -C, C, C, C, C, -C and related security functions, C, -C, C, C, C, -C, C, C, C, C, -C<*netent()>, C<*protoent()>, C<*servent()>, C<*hostent()>, -C. -This list is possibly incomplete. - -=item * - -Various C related calls are supported, but they may not -behave as on Unix platforms. - -=item * - -The four-argument C call is only supported on sockets. - -=item * - -The C call is only supported on sockets (where it provides the -functionality of ioctlsocket() in the Winsock API). - -=item * - -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). - -=item * - -You can expect problems building modules available on CPAN if you -build perl itself with -DUSE_THREADS. These problems should be resolved -as we get closer to 5.005. - -=item * - -C, C and process-related functions may not -behave as described in the documentation, and some of the -returned values or effects may be bogus. - -=item * - -Signal handling may not behave as on Unix platforms (where it -doesn't exactly "behave", either :). For instance, calling C -or C from signal handlers will cause an exception, since most -implementations of C 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. - -=item * - -C is implemented, but 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 it immediately calls -C. Thus the signal argument is -used to set the exit-status of the terminated process. However, -a signal of 0 can be used to safely check if the specified process -exists, as on Unix. - -=item * - -File globbing may not behave as on Unix platforms. In particular, -if you don't use perlglob.bat for globbing, it will understand -wildcards only in the filename component (and not in the pathname). -In other words, something like "print <*/*.pl>" will not print all the -perl scripts in all the subdirectories one level under the current one -(like it does on UNIX platforms). perlglob.exe is also dependent on -the particular implementation of wildcard expansion in the vendor -libraries used to build it (which varies wildly at the present time). -Using perlglob.bat (or File::DosGlob) avoids these limitations, but -still only provides DOS semantics (read "warts") for globbing. - -=back - +In the Win32 port, some of Perl's built-in functions do not act +exactly as documented in L, and a few are not +implemented at all. To avoid surprises, particularly if you have had +prior exposure to Perl in other operating environments, see +L for a reasonably definitive list of functions which are +either not implemented under Win32, or whose behavior in the Win32 +environment differs markedly from that elsewhere. You will also find +L useful if you wish to write Perl programs which are +portable across operating environments. + +Not all of the extensions available from CPAN are known or intended to +work in the Win32 environment -- see L. + +The limitations in the WIn32 implementation of Perl (which, in any +event, diminish with each release of Perl) are not considered serious +(especially when compared to the +limited nature of some of the Win32 OSes themselves :). Nevertheless, Please send detailed descriptions of any problems and solutions that you may find to >, along with the output produced by C. @@ -741,6 +671,8 @@ Win9x support was added in 5.6 (Benjamin Stuhl). -Last updated: 28 December 1999 +Now refers readers to L for list of behavior differences. + +Last updated: 13 March 2000 =cut -- Dominic Dunlop ```

From [Unknown Contact. See original ticket]

On Tue\, 14 Mar 2000\, Dominic Dunlop wrote:

- http://cpan.perl.org/authors/id/GSAR/dmake-4.1pl1-win32.zip + http://www.cpan.org/authors/Gurusamy_Sarathy/dmake-4.1pl1-win32.zip

- http://www.perl.com/CPAN/authors/id/NI-S/Make-0.03.tar.gz + http://www.cpan.org/authors/Nick_Ing-Simmons/Make-1.00.tar.gz

- http://www.perl.com/CPAN/authors/id/GSAR/libwin32-0.14.zip + http://www.cpan.org/authors/Gurusamy_Sarathy/libwin32-0.151.zip

Isn't the canonical path for CPAN directories the authors/id/ version? Especially since the "verbose" links in authors/ are no longer maintained\, and http://www.cpan.org/authors/00.Directory.Is.Not.Maintained.Anymore says that the directory is expected to go away in the future (except for the subdirectory id).

The same file mentioned above also says that "every click on this directory entry costs a lot of time" and that "they cannot be removed because lots of people have made links to individual entries here.

Cheers\, Philip -- Philip Newton \newton@newton\.digitalspace\.net

From [Unknown Contact. See original ticket]

The same file mentioned above also says that "every click on this directory entry costs a lot of time"

I find that a bit silly. Apparently the writer and I have different ideas of "a lot".

--tom

From [Unknown Contact. See original ticket]

On Tue\, 14 Mar 2000\, Tom Christiansen wrote:

The same file mentioned above also says that "every click on this directory entry costs a lot of time"

I find that a bit silly. Apparently the writer and I have different ideas of "a lot".

I\, too\, wondered about that. How does accessing those directories cost extra time? If I understand correctly\, it's just a symbolic link to traverse\, which shouldn't be that costly.

Cheers\, Philip -- Philip Newton \newton@newton\.digitalspace\.net

From [Unknown Contact. See original ticket]

The same file mentioned above also says that "every click on this directory entry costs a lot of time"

I find that a bit silly. Apparently the writer and I have different ideas of "a lot".

I\, too\, wondered about that. How does accessing those directories cost extra time? If I understand correctly\, it's just a symbolic link to traverse\, which shouldn't be that costly.

Every click is sacred. Every click is great. If a click is wasted\, Root gets quite irate.

--tom

From [Unknown Contact. See original ticket]

Philip Newton \newton@newton\.digitalspace\.net writes:

I\, too\, wondered about that. How does accessing those directories cost extra time? If I understand correctly\, it's just a symbolic link to traverse\, which shouldn't be that costly.

Think "single large directory" and note that the authors/id space is being restructured into subdirectories.

-- Russ Allbery (rra@stanford.edu) \<http://www.eyrie.org/~eagle/>

From [Unknown Contact. See original ticket]

Philip Newton \newton@newton\.digitalspace\.net writes:

I\, too\, wondered about that. How does accessing those directories cost extra time? If I understand correctly\, it's just a symbolic link to traverse\, which shouldn't be that costly.

Think "single large directory" and note that the authors/id space is being restructured into subdirectories.

namei() is a very busy beaver on big directories. And on Linux filesystems\, it takes O(n) time\, although I believe on BSD\, it takes like O(log n) time. If that's really it\, then that's why find and whatever -R take 10x the time on Linux for recurses down through big fat directories compared with the same on BSD. They make up for it in other ways\, occasionally\, like with asynchronous directory updates--well\, if you can call that a feature; fsck sometimes does not. :-(

--tom

From [Unknown Contact. See original ticket]

On 14 Mar 2000\, Russ Allbery wrote:

Philip Newton \newton@newton\.digitalspace\.net writes:

I\, too\, wondered about that. How does accessing those directories cost extra time? If I understand correctly\, it's just a symbolic link to traverse\, which shouldn't be that costly.

Think "single large directory" and note that the authors/id space is being restructured into subdirectories.

Because each of the single-letter subdirectories was getting too big?

Cheers\, Philip -- Philip Newton \newton@newton\.digitalspace\.net

From @timbunce

On Tue\, Mar 14\, 2000 at 07:15:36AM -0800\, Russ Allbery wrote:

Philip Newton \newton@newton\.digitalspace\.net writes:

I\, too\, wondered about that. How does accessing those directories cost extra time? If I understand correctly\, it's just a symbolic link to traverse\, which shouldn't be that costly.

Think "single large directory" and note that the authors/id space is being restructured into subdirectories.

Yes. Tom would probably know that as the "indirect inode" problem that most unix systems have with very large directories. The authors directory just won't scale. Thats why new PAUSE authors only get directories like authors/id/F/FO/FOO.

Tim.

From @gsar

On Tue\, 14 Mar 2000 11:05:34 +0100\, Dominic Dunlop wrote:

There's more work to be done by somebody who knows more about the port than I do. For example\, there's no mention whatever in the README of Windows 98\, never mind 2000; and the notes on globbing need attention now that perl does it without an external helper. (This is true of perlport.pod as well.)

Thanks. This should be a little better.

Sarathy gsar@ActiveState.com

Inline Patch

```diff -----------------------------------8<----------------------------------- Change 5731 by gsar@auger on 2000/03/14 17:15:44 revise README.win32 for currentness, point to function list in perlport.pod (from a patch suggested by Dominic Dunlop) Affected files ... ... //depot/perl/README.win32#35 edit ... //depot/perl/pod/perlport.pod#33 edit Differences ... ==== //depot/perl/README.win32#35 (text) ==== Index: perl/README.win32 --- perl/README.win32.~1~ Tue Mar 14 09:16:40 2000 +++ perl/README.win32 Tue Mar 14 09:16:40 2000 @@ -8,13 +8,8 @@ =head1 SYNOPSIS -These are instructions for building Perl under Windows NT (versions -3.51 or 4.0). Currently, this port is reported to build under -Windows95 using the 4DOS shell--the default shell that infests -Windows95 may not work fully (but see below). Note that this caveat -is only about B perl. Once built, you should be able to -B it on either Win32 platform (modulo the problems arising from -the inferior command shell). +These are instructions for building Perl under Windows (9x, NT and +2000). =head1 DESCRIPTION @@ -62,19 +57,37 @@ =over 4 +=item Make + +You need a "make" program to build the sources. If you are using +Visual C++ under Windows NT or 2000, nmake will work. All other +builds need dmake. + +dmake is a freely available make that has very nice macro features +and parallelability. + +A port of dmake for Windows is available from: + + http://www.cpan.org/authors/id/GSAR/dmake-4.1pl1-win32.zip + +(This is a fixed version of original dmake sources obtained from +http://www.wticorp.com/dmake/. As of version 4.1PL1, the original +sources did not build as shipped, and had various other problems. +A patch is included in the above fixed version.) + +Fetch and install dmake somewhere on your path (follow the instructions +in the README.NOW file). + =item Command Shell Use the default "cmd" shell that comes with NT. Some versions of the popular 4DOS/NT shell have incompatibilities that may cause you trouble. If the build fails under that shell, try building again with the cmd -shell. The nmake Makefile also has known incompatibilites with the -"command.com" shell that comes with Windows95. +shell. -However, there have been reports of successful build attempts using -4DOS/NT version 6.01 under Windows95, using dmake, but your mileage -may vary. There is also some basic support for building using dmake -under command.com. Nevertheless, if building under command.com -doesn't work, try 4DOS/NT. +The nmake Makefile also has known incompatibilites with the +"command.com" shell that comes with Windows 9x. You will need to +use dmake and makefile.mk to build under Windows 9x. The surest way to build it is on Windows NT, using the cmd shell. @@ -83,23 +96,12 @@ =item Borland C++ -If you are using the Borland compiler, you will need dmake, a freely -available make that has very nice macro features and parallelability. +If you are using the Borland compiler, you will need dmake. (The make that Borland supplies is seriously crippled, and will not work for MakeMaker builds.) -A port of dmake for win32 platforms is available from: - - http://cpan.perl.org/authors/id/GSAR/dmake-4.1pl1-win32.zip +See L/"Make"> above. -(This is a fixed version of original dmake sources obtained from -http://www.wticorp.com/dmake/. As of version 4.1PL1, the original -sources did not build as shipped, and had various other problems. -A patch is included in the above fixed version.) - -Fetch and install dmake somewhere on your path (follow the instructions -in the README.NOW file). - =item Microsoft Visual C++ The nmake that comes with Visual C++ will suffice for building. @@ -125,7 +127,7 @@ in the README for the GCC bundle. You may need to set up a few environment variables (usually run from a batch file). -You also need dmake. See L above on how to get it. +You also need dmake. See L above on how to get it. =back @@ -139,40 +141,21 @@ This directory contains a "Makefile" that will work with versions of nmake that come with Visual C++, and a dmake "makefile.mk" that will work for all supported compilers. The defaults in the dmake -makefile are setup to build using the Borland compiler. +makefile are setup to build using the GCC compiler. =item * Edit the makefile.mk (or Makefile, if using nmake) and change the values of INST_DRV and INST_TOP. You can also enable various build -flags. +flags. These are explained in the makefiles. -Beginning with version 5.005, there is experimental support for building -a perl interpreter that supports the Perl Object abstraction (courtesy -ActiveState Tool Corp.) PERL_OBJECT uses C++, and the binaries are -therefore incompatible with the regular C build. However, the -PERL_OBJECT build does provide something called the C-API, for linking -it with extensions that won't compile under PERL_OBJECT. Using the C_API -is typically requested through: +You will have to make sure CCTYPE is set correctly, and CCHOME points +to wherever you installed your compiler. - perl Makefile.PL CAPI=TRUE +The default value for CCHOME in the makefiles for Visual C++ +may not be correct for some versions. Make sure the default exists +and is valid. -PERL_OBJECT requires VC++ 5.0 (Service Pack 3 recommended) or later. It -is not yet supported under GCC. WARNING: Binaries built with -PERL_OBJECT enabled are B compatible with binaries built without. -Perl installs PERL_OBJECT binaries under a distinct architecture name, -so they B coexist, though. - -Beginning with version 5.005, there is experimental support for building -a perl interpreter that is capable of native threading. Binaries built -with thread support enabled are also incompatible with the vanilla C -build. WARNING: Binaries built with threads enabled are B compatible -with binaries built without. Perl installs threads enabled binaries under -a distinct architecture name, so they B coexist, though. - -At the present time, you cannot enable both threading and PERL_OBJECT. -You can get only one of them in a Perl interpreter. - If you have either the source or a library that contains des_fcrypt(), enable the appropriate option in the makefile. des_fcrypt() is not bundled with the distribution due to US Government restrictions @@ -192,35 +175,24 @@ Perl will also build without des_fcrypt(), but the crypt() builtin will fail at run time. -You will also have to make sure CCHOME points to wherever you installed -your compiler. - -The default value for CCHOME in the makefiles for Visual C++ -may not be correct for some versions. Make sure the default exists -and is valid. - -Other options are explained in the makefiles. Be sure to read the -instructions carefully. +Be sure to read the instructions near the top of the makefiles carefully. =item * Type "dmake" (or "nmake" if you are using that make). This should build everything. Specifically, it will create perl.exe, -perl.dll (or perl56.dll), and perlglob.exe at the perl toplevel, and -various other extension dll's under the lib\auto directory. If the build -fails for any reason, make sure you have done the previous steps correctly. +perl56.dll at the perl toplevel, and various other extension dll's +under the lib\auto directory. If the build fails for any reason, make +sure you have done the previous steps correctly. -The build process may produce "harmless" compiler warnings (more or -less copiously, depending on how picky your compiler gets). The -maintainers are aware of these warnings, thankyouverymuch. :) - =back =head2 Testing Type "dmake test" (or "nmake test"). This will run most of the tests from -the testsuite (many tests will be skipped, and but no test should fail). +the testsuite (many tests will be skipped, but no tests should typically +fail). If some tests do fail, it may be because you are using a different command shell than the native "cmd.exe", or because you are building from a path @@ -248,8 +220,13 @@ C<$INST_TOP\$VERSION\bin>, and C<$INST_TOP\$VERSION\bin\$ARCHNAME>. For example: - set PATH c:\perl\5.005\bin;c:\perl\5.005\bin\MSWin32-x86;%PATH% + set PATH c:\perl\5.6.0\bin;c:\perl\5.6.0\bin\MSWin32-x86;%PATH% + +If you opt to comment out INST_VER and INST_ARCH in the makefiles, the +installation structure is much simpler. In that case, it will be +sufficient to add a single entry to the path, for instance: + set PATH c:\perl\bin;%PATH% =head2 Usage Hints @@ -289,32 +266,19 @@ =item File Globbing -By default, perl spawns an external program to do file globbing. -The install process installs both a perlglob.exe and a perlglob.bat -that perl can use for this purpose. Note that with the default -installation, perlglob.exe will be found by the system before -perlglob.bat. +By default, perl handles file globbing using the File::Glob extension, +which provides portable globbing. -perlglob.exe relies on the argv expansion done by the C Runtime of -the particular compiler you used, and therefore behaves very -differently depending on the Runtime used to build it. To preserve -compatiblity, perlglob.bat (a perl script that can be used portably) -is installed. Besides being portable, perlglob.bat also offers -enhanced globbing functionality. - -If you want perl to use perlglob.bat instead of perlglob.exe, just -delete perlglob.exe from the install location (or move it somewhere -perl cannot find). Using File::DosGlob.pm (which implements the core -functionality of perlglob.bat) to override the internal CORE::glob() -works about 10 times faster than spawing perlglob.exe, and you should -take this approach when writing new modules. See File::DosGlob for +If you want perl to use globbing that emulates the quirks of DOS +filename conventions, you might want to consider using File::DosGlob +to override the internal glob() implementation. See L for details. =item Using perl from the command line If you are accustomed to using perl from various command-line shells found in UNIX environments, you will be less than pleased -with what Windows NT offers by way of a command shell. +with what Windows offers by way of a command shell. The crucial thing to understand about the "cmd" shell (which is the default on Windows NT) is that it does not do any wildcard @@ -375,14 +339,19 @@ perl -e "print 'foo'; print STDERR 'bar'" 2> blurch | less -Discovering the usefulness of the "command.com" shell on Windows95 +Discovering the usefulness of the "command.com" shell on Windows 9x is left as an exercise to the reader :) =item Building Extensions The Comprehensive Perl Archive Network (CPAN) offers a wealth of extensions, some of which require a C compiler to build. -Look in http://www.perl.com/ for more information on CPAN. +Look in http://www.cpan.org/ for more information on CPAN. + +Note that not all of the extensions available from CPAN may work +in the Win32 environment; you should check the information at +http://testers.cpan.org/ before investing too much effort into +porting modules that don't readily build. Most extensions (whether they require a C compiler or not) can be built, tested and installed with the standard mantra: @@ -407,9 +376,9 @@ Another option is to use the make written in Perl, available from CPAN: - http://www.perl.com/CPAN/authors/id/NI-S/Make-0.03.tar.gz + http://www.cpan.org/authors/id/NI-S/Make-0.03.tar.gz -You may also use dmake. See L above on how to get it. +You may also use dmake. See L above on how to get it. Note that MakeMaker actually emits makefiles with different syntax depending on what 'make' it thinks you are using. Therefore, it is @@ -502,7 +471,7 @@ CPAN in source form, along with many added bugfixes, and with MakeMaker support. This bundle is available at: - http://www.perl.com/CPAN/authors/id/GSAR/libwin32-0.14.zip + http://www.cpan.org/authors/id/GSAR/libwin32-0.151.zip See the README in that distribution for building and installation instructions. Look for later versions that may be available at the @@ -599,76 +568,19 @@ =head1 BUGS AND CAVEATS -An effort has been made to ensure that the DLLs produced by the two -supported compilers are compatible with each other (despite the -best efforts of the compiler vendors). Extension binaries produced -by one compiler should also coexist with a perl binary built by -a different compiler. In order to accomplish this, PERL.DLL provides -a layer of runtime code that uses the C Runtime that perl was compiled -with. Extensions which include "perl.h" will transparently access -the functions in this layer, thereby ensuring that both perl and -extensions use the same runtime functions. +Some of the built-in functions do not act exactly as documented in +L, 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 L +for a reasonably definitive list of these differences. -If you have had prior exposure to Perl on Unix platforms, you will notice -this port exhibits behavior different from what is documented. Most of the -differences fall under one of these categories. We do not consider -any of them to be serious limitations (especially when compared to the -limited nature of some of the Win32 OSes themselves :) +Not all extensions available from CPAN may build or work properly +in the Win32 environment. See L. -=over 8 - -=item * - -C and C functions may not behave as documented. They -may return values that bear no resemblance to those reported on Unix -platforms, and some fields (like the the one for inode) may be completely -bogus. - -=item * - -The following functions are currently unavailable: C, -C, C, C, C, C, -C and related security functions, C, -C, C, C, C, -C, C, C, C, C, -C<*netent()>, C<*protoent()>, C<*servent()>, C<*hostent()>, -C. -This list is possibly incomplete. - -=item * - -Various C related calls are supported, but they may not -behave as on Unix platforms. - -=item * - -The four-argument C call is only supported on sockets. - -=item * - -The C call is only supported on sockets (where it provides the -functionality of ioctlsocket() in the Winsock API). - -=item * - -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). - -=item * - -You can expect problems building modules available on CPAN if you -build perl itself with -DUSE_THREADS. These problems should be resolved -as we get closer to 5.005. - -=item * +Most C related calls are supported, but they may not +behave as on Unix platforms. See L for the full list. -C, C and process-related functions may not -behave as described in the documentation, and some of the -returned values or effects may be bogus. - -=item * - Signal handling may not behave as on Unix platforms (where it doesn't exactly "behave", either :). For instance, calling C or C from signal handlers will cause an exception, since most @@ -677,31 +589,6 @@ variable in the handler. Using signals under this port should currently be considered unsupported. -=item * - -C is implemented, but 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 it immediately calls -C. Thus the signal argument is -used to set the exit-status of the terminated process. However, -a signal of 0 can be used to safely check if the specified process -exists, as on Unix. - -=item * - -File globbing may not behave as on Unix platforms. In particular, -if you don't use perlglob.bat for globbing, it will understand -wildcards only in the filename component (and not in the pathname). -In other words, something like "print <*/*.pl>" will not print all the -perl scripts in all the subdirectories one level under the current one -(like it does on UNIX platforms). perlglob.exe is also dependent on -the particular implementation of wildcard expansion in the vendor -libraries used to build it (which varies wildly at the present time). -Using perlglob.bat (or File::DosGlob) avoids these limitations, but -still only provides DOS semantics (read "warts") for globbing. - -=back - Please send detailed descriptions of any problems and solutions that you may find to >, along with the output produced by C. @@ -741,6 +628,6 @@ Win9x support was added in 5.6 (Benjamin Stuhl). -Last updated: 28 December 1999 +Last updated: 13 March 2000 =cut ==== //depot/perl/pod/perlport.pod#33 (text) ==== Index: perl/pod/perlport.pod --- perl/pod/perlport.pod.~1~ Tue Mar 14 09:16:40 2000 +++ perl/pod/perlport.pod Tue Mar 14 09:16:40 2000 @@ -1223,6 +1223,12 @@ 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) @@ -1444,15 +1450,9 @@ 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) +This operator is implemented via the File::Glob extension on most +platforms. See L for portability information. -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) - =item ioctl FILEHANDLE,FUNCTION,SCALAR Not implemented. (VMS) @@ -1467,9 +1467,12 @@ Not implemented, hence not useful for taint checking. (S, S) -C makes the process 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) +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 @@ -1489,7 +1492,7 @@ 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 @@ -1531,6 +1534,8 @@ Only reliable on sockets. (S) +Note that the C form is generally portable. + =item semctl ID,SEMNUM,CMD,ARG =item semget KEY,NSEMS,FLAGS @@ -1612,7 +1617,10 @@ 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 @@ -1636,9 +1644,10 @@ 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) End of Patch. ```

Perl / perl5

flock( ) #1330

From ratsim@yahoo.fr

Created by ratsim@yahoo.fr

From [Unknown Contact. See original ticket]

From @gsar

From [Unknown Contact. See original ticket]

From [Unknown Contact. See original ticket]

From [Unknown Contact. See original ticket]

From [Unknown Contact. See original ticket]

From [Unknown Contact. See original ticket]

From [Unknown Contact. See original ticket]

From [Unknown Contact. See original ticket]

From [Unknown Contact. See original ticket]

From @timbunce

From @gsar