better {local,gm}time documentation (from Mark-Jason Dominus)

[p5sagit/p5-mst-13.2.git] / README.win32

diff --git a/README.win32 b/README.win32
index 5499d3a..b39961b 100644 (file)
--- a/README.win32
+++ b/README.win32
@@ -275,14 +275,16 @@ C<HKEY_CURRENT_USER\Software\Perl> and C<HKEY_LOCAL_MACHINE\Software\Perl>.
 Entries in the former override entries in the latter.  One or more of the
 following entries (of type REG_SZ or REG_EXPAND_SZ) may be set:
 
-    lib-$]             version-specific path to add to @INC
-    lib                        path to add to @INC
-    sitelib-$]         version-specific path to add to @INC
-    sitelib            path to add to @INC
+    lib-$]             version-specific standard library path to add to @INC
+    lib                        standard library path to add to @INC
+    sitelib-$]         version-specific site library path to add to @INC
+    sitelib            site library path to add to @INC
+    vendorlib-$]       version-specific vendor library path to add to @INC
+    vendorlib          vendor library path to add to @INC
     PERL*              fallback for all %ENV lookups that begin with "PERL"
 
 Note the C<$]> in the above is not literal.  Substitute whatever version
-of perl you want to honor that entry, e.g. C<5.00502>.  Paths must be
+of perl you want to honor that entry, e.g. C<5.6.0>.  Paths must be
 separated with semicolons, as usual on win32.
 
 =item File Globbing
@@ -407,6 +409,8 @@ CPAN:
 
     http://www.perl.com/CPAN/authors/id/NI-S/Make-0.03.tar.gz
 
+You may also use dmake.  See L</"Borland C++"> 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
 important that one of the following values appears in Config.pm:
@@ -679,9 +683,9 @@ C<kill()> is implemented, but doesn't have the semantics of
 C<raise()>, i.e. it doesn't send a signal to the identified process
 like it does on Unix platforms.  Instead it immediately calls
 C<TerminateProcess(process,signal)>.  Thus the signal argument is
-used to set the exit-status of the terminated process.  In particular,
-C<kill(0,$pid)> will kill the process identified by C<$pid> (unlike
-on Unix).  This behavior may change in future.
+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 *