s/PL_sv/PL_bytecode_sv/ etc., so we have unique, case-insensitive

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

diff --git a/README.win32 b/README.win32
index 873df29..3ba6d2e 100644 (file)
--- a/README.win32
+++ b/README.win32
@@ -50,7 +50,8 @@ following compilers:
       Mingw32 with EGCS                version 1.0.2
       Mingw32 with GCC         version 2.8.1
 
-The last two of these are high quality freeware compilers.
+The last two of these are high quality freeware compilers.  Support
+for them is still experimental.
 
 This port currently supports MakeMaker (the set of modules that
 is used to build extensions to perl).  Therefore, you should be
@@ -145,7 +146,8 @@ 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.
+it with extensions that won't compile under PERL_OBJECT.  PERL_OBJECT
+cannot be enabled when using GCC or EGCS, yet.
 
 Beginning with version 5.005, there is experimental support for building
 a perl interpreter that is capable of native threading.  Binaries built
@@ -573,6 +575,15 @@ currently be considered unsupported.
 
 =item *
 
+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.  This behavior
+may change in future.
+
+=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).