From 7a1882f63dfcfc625b6b7f039daf83c563ff6016 Mon Sep 17 00:00:00 2001
From: Hartmut Holzgraefe <hholzgra@php.net>
Date: Fri, 3 Jun 2005 00:46:55 +0000
Subject: [PATCH] added warning about setlocale() not being thread safe

git-svn-id: https://svn.php.net/repository/phpdoc/en/trunk@187536 c90b9560-bf6c-de11-be94-00142212c4b1
---
 reference/strings/functions/setlocale.xml | 14 +++++++++++++-
 1 file changed, 13 insertions(+), 1 deletion(-)

diff --git a/reference/strings/functions/setlocale.xml b/reference/strings/functions/setlocale.xml
index f3c3da24f1..543846612f 100644
--- a/reference/strings/functions/setlocale.xml
+++ b/reference/strings/functions/setlocale.xml
@@ -1,5 +1,5 @@
 <?xml version="1.0" encoding="iso-8859-1"?>
-<!-- $Revision: 1.22 $ -->
+<!-- $Revision: 1.23 $ -->
 <!-- splitted from ./en/functions/strings.xml, last change in rev 1.2 -->
   <refentry id="function.setlocale">
    <refnamediv>
@@ -104,6 +104,18 @@
       what the system setlocale function returns.
      </para>
     </note>
+    <warning>
+     <para>
+      The locale information is maintained per process, not per
+      thread. If you are running PHP on a multithreaded server 
+      api like IIS or Apache on Windows you may experience 
+      sudden changes of locale settings while a script is 
+      running although the script itself never called <function>setlocale()</function>
+      itself. This happens due to other scripts running in different
+      threads of the same process at the same time changing the
+      processwide locale using <function>setlocale</function>.
+     </para>
+    </warning>
     <tip>
      <para>
       Windows users will find useful information about