From 5f03a641c83e5f27a7a36d3e5d527aaed1e4ca92 Mon Sep 17 00:00:00 2001 From: Joe Watkins Date: Wed, 10 Apr 2013 11:48:44 +0000 Subject: [PATCH] clarity git-svn-id: https://svn.php.net/repository/phpdoc/en/trunk@330056 c90b9560-bf6c-de11-be94-00142212c4b1 --- internals2/memory/TSRM.xml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/internals2/memory/TSRM.xml b/internals2/memory/TSRM.xml index 2196cb389e..ee96eaa7e7 100644 --- a/internals2/memory/TSRM.xml +++ b/internals2/memory/TSRM.xml @@ -29,7 +29,7 @@ - If a function requires a pointer to TSRM, it is declared with the macro TSRMLS_D or TSRMLS_DC in it's prototype, wihch translates to "thread safe local storage only" and "thread safe local storage prefixed with a comma" respectively. Many macros within the engine reference TSRM, so it is a good idea to declare most things to accept TSRM, such that if they need to call upon TSRM they do not have to fetch a pointer during execution, whenever PHP is built in Thread Safe mode TSRM is available by default. + If a function requires a pointer to TSRM, it is declared with the macro TSRMLS_D or TSRMLS_DC in it's prototype, wihch translates to "thread safe local storage only" and "thread safe local storage prefixed with a comma" respectively. Many macros within the engine reference TSRM, so it is a good idea to declare most things to accept TSRM, such that if they need to call upon TSRM they do not have to fetch a pointer during execution. @@ -43,7 +43,7 @@ - The functionality documented hereafter is aimed at advanced use of TSRM. It is not ordinary for extensions to have to interact with TSRM directly, the pecl programmer should use API's above TSRM such as the Module Globals API which used correctly will ensure safety in ZTS mode for you. + The functionality documented hereafter is aimed at advanced use of TSRM. It is not ordinary for extensions to have to interact with TSRM directly, the pecl programmer should use API's above TSRM such as the Module Globals API.