diff --git a/el-GR/config.md b/el-GR/config.md index 3537a0365..d32c86274 100644 --- a/el-GR/config.md +++ b/el-GR/config.md @@ -180,7 +180,7 @@ Extension description - any text describing your extension: ## destructors -This setting lets you provide one or more C functions to be executed on certain extension lifecycle events - specifically, `RSHUTDOWN` (`request`), `PRSHUTDOWN` (`post-request`), `MSHUTDOWN` (`module`), and `GSHUTDOWN` (`globals`). Check the [lifecycle hooks](/[[language]]/[[version]]/lifecycle) chapter for more information. +This setting lets you provide one or more C functions to be executed on certain extension lifecycle events - specifically, `RSHUTDOWN` (`request`), `PRSHUTDOWN` (`post-request`), `MSHUTDOWN` (`module`), and `GSHUTDOWN` (`globals`). Check the [lifecycle hooks](/{{ page.version }}/{{ page.language }}/lifecycle) chapter for more information. ```json { @@ -306,7 +306,7 @@ Any additional files you want to add to the compilation process - the search dir ## globals -Extension globals available. Check the [globals](/[[language]]/[[version]]/globals) chapter for more information. +Extension globals available. Check the [globals](/{{ page.version }}/{{ page.language }}/globals) chapter for more information. ```json { @@ -325,7 +325,7 @@ Extension globals available. Check the [globals](/[[language]]/[[version]]/globa ## info -`phpinfo()` sections. Check the [phpinfo()](/[[language]]/[[version]]/phpinfo) chapter for more information. +`phpinfo()` sections. Check the [phpinfo()](/{{ page.version }}/{{ page.language }}/phpinfo) chapter for more information. ```json { @@ -343,7 +343,7 @@ Extension globals available. Check the [globals](/[[language]]/[[version]]/globa ## initializers -This setting lets you provide one or more C functions to be executed on certain extension lifecycle events - specifically, `GINIT` (`globals`), `MINIT` (`module`), and `RINIT` (`request`). Check the [lifecycle hooks](/[[language]]/[[version]]/lifecycle) chapter for more information. +This setting lets you provide one or more C functions to be executed on certain extension lifecycle events - specifically, `GINIT` (`globals`), `MINIT` (`module`), and `RINIT` (`request`). Check the [lifecycle hooks](/{{ page.version }}/{{ page.language }}/lifecycle) chapter for more information. ```json { diff --git a/el-GR/lifecycle.md b/el-GR/lifecycle.md index 62036a538..5811dfbd4 100644 --- a/el-GR/lifecycle.md +++ b/el-GR/lifecycle.md @@ -18,7 +18,7 @@ Consider the following diagram: ![The PHP Process/Request Lifecycle](/assets/content/lifecycle.png) -Lifecycle hooks are registered in the `config.json` file. As you can see in the diagram above, there are four types of lifecycle hooks - `globals`, `initializers`, `destructors`, and `info`. Each of these has its own corresponding root-level setting in the configuration, and both [globals](/[[language]]/[[version]]/globals) and [info](/[[language]]/[[version]]/phpinfo) have their own chapters. This chapter covers the other two settings. +Lifecycle hooks are registered in the `config.json` file. As you can see in the diagram above, there are four types of lifecycle hooks - `globals`, `initializers`, `destructors`, and `info`. Each of these has its own corresponding root-level setting in the configuration, and both [globals](/{{ page.version }}/{{ page.language }}/globals) and [info](/{{ page.version }}/{{ page.language }}/phpinfo) have their own chapters. This chapter covers the other two settings. Each hook in the `config.json` file is an array of objects, which themselves are essentially `include`/`code` pairs. The `include` value will pull in a given C header file, if it hasn't been already, so that the `code` will have access to its contents. The `code` value is the logic run by the hook itself, and while you can technically put any valid C in here, it is ***strongly*** recommended to put logic longer than one or two lines into a separate C source file (such as the one pulled in along with your `include`d header file), and use a single-line function call here. @@ -103,4 +103,4 @@ The `destructors` block looks something like this: } ``` -Much as the `initializers` block is responsible for defining hooks into the Init events shown in the diagram above, *this* block is responsible for defining hooks into the Shutdown events. There are four of these: `request` for finalizing any data before a response is sent to the client, `post-request` for cleaning up after a response has been sent, `module` for cleaning up after the extension itself before the PHP process shuts down, and `globals` for cleaning up the global variable space. \ No newline at end of file +Much as the `initializers` block is responsible for defining hooks into the Init events shown in the diagram above, *this* block is responsible for defining hooks into the Shutdown events. There are four of these: `request` for finalizing any data before a response is sent to the client, `post-request` for cleaning up after a response has been sent, `module` for cleaning up after the extension itself before the PHP process shuts down, and `globals` for cleaning up the global variable space. diff --git a/el-GR/optimizers.md b/el-GR/optimizers.md index e436652d3..7b047672e 100644 --- a/el-GR/optimizers.md +++ b/el-GR/optimizers.md @@ -171,7 +171,7 @@ This file must contain the Zend Engine headers, and the C implementation of the } -This file must be added at a special section in the [config.json](/[[language]]/[[version]]/config) file: +This file must be added at a special section in the [config.json](/{{ page.version }}/{{ page.language }}/config) file: "extra-sources": [ "utils/pi.c" @@ -185,4 +185,4 @@ Lastly you will have to specify where Zephir can find your optimizer by using th ] -Check the complete source code of this example [here](https://github.com/phalcon/zephir-samples/tree/master/ext-optimizers) \ No newline at end of file +Check the complete source code of this example [here](https://github.com/phalcon/zephir-samples/tree/master/ext-optimizers) diff --git a/el-GR/tutorial.md b/el-GR/tutorial.md index 33712b609..e763b263f 100644 --- a/el-GR/tutorial.md +++ b/el-GR/tutorial.md @@ -78,7 +78,7 @@ If everything is well, you should see the following help (or something very simi -W([a-z0-9\-]+) Turns a warning off -If something went wrong, please return back to the [installation](/[[language]]/[[version]]/installation) page. +If something went wrong, please return back to the [installation](/{{ page.version }}/{{ page.language }}/installation) page. @@ -278,4 +278,4 @@ In the following screencast you can watch how to create the extension explained ## Conclusion -This is a very simple tutorial, and as you can see, it's easy to start building extensions using Zephir. We invite you to continue reading the manual so that you can discover additional features offered by Zephir! \ No newline at end of file +This is a very simple tutorial, and as you can see, it's easy to start building extensions using Zephir. We invite you to continue reading the manual so that you can discover additional features offered by Zephir! diff --git a/en/config.md b/en/config.md index 493c48e17..71b8ffa8a 100644 --- a/en/config.md +++ b/en/config.md @@ -180,7 +180,7 @@ Extension description - any text describing your extension: ## destructors -This setting lets you provide one or more C functions to be executed on certain extension lifecycle events - specifically, `RSHUTDOWN` (`request`), `PRSHUTDOWN` (`post-request`), `MSHUTDOWN` (`module`), and `GSHUTDOWN` (`globals`). Check the [lifecycle hooks](/[[language]]/[[version]]/lifecycle) chapter for more information. +This setting lets you provide one or more C functions to be executed on certain extension lifecycle events - specifically, `RSHUTDOWN` (`request`), `PRSHUTDOWN` (`post-request`), `MSHUTDOWN` (`module`), and `GSHUTDOWN` (`globals`). Check the [lifecycle hooks](/{{ page.version }}/{{ page.language }}/lifecycle) chapter for more information. ```json { @@ -306,7 +306,7 @@ Any additional files you want to add to the compilation process - the search dir ## globals -Extension globals available. Check the [globals](/[[language]]/[[version]]/globals) chapter for more information. +Extension globals available. Check the [globals](/{{ page.version }}/{{ page.language }}/globals) chapter for more information. ```json { @@ -325,7 +325,7 @@ Extension globals available. Check the [globals](/[[language]]/[[version]]/globa ## info -`phpinfo()` sections. Check the [phpinfo()](/[[language]]/[[version]]/phpinfo) chapter for more information. +`phpinfo()` sections. Check the [phpinfo()](/{{ page.version }}/{{ page.language }}/phpinfo) chapter for more information. ```json { @@ -343,7 +343,7 @@ Extension globals available. Check the [globals](/[[language]]/[[version]]/globa ## initializers -This setting lets you provide one or more C functions to be executed on certain extension lifecycle events - specifically, `GINIT` (`globals`), `MINIT` (`module`), and `RINIT` (`request`). Check the [lifecycle hooks](/[[language]]/[[version]]/lifecycle) chapter for more information. +This setting lets you provide one or more C functions to be executed on certain extension lifecycle events - specifically, `GINIT` (`globals`), `MINIT` (`module`), and `RINIT` (`request`). Check the [lifecycle hooks](/{{ page.version }}/{{ page.language }}/lifecycle) chapter for more information. ```json { diff --git a/en/lifecycle.md b/en/lifecycle.md index 80e0c6254..bdeedb243 100644 --- a/en/lifecycle.md +++ b/en/lifecycle.md @@ -17,7 +17,7 @@ Consider the following diagram: ![The PHP Process/Request Lifecycle](/assets/content/lifecycle.png) -Lifecycle hooks are registered in the `config.json` file. As you can see in the diagram above, there are four types of lifecycle hooks - `globals`, `initializers`, `destructors`, and `info`. Each of these has its own corresponding root-level setting in the configuration, and both [globals](/[[language]]/[[version]]/globals) and [info](/[[language]]/[[version]]/phpinfo) have their own chapters. This chapter covers the other two settings. +Lifecycle hooks are registered in the `config.json` file. As you can see in the diagram above, there are four types of lifecycle hooks - `globals`, `initializers`, `destructors`, and `info`. Each of these has its own corresponding root-level setting in the configuration, and both [globals](/{{ page.version }}/{{ page.language }}/globals) and [info](/{{ page.version }}/{{ page.language }}/phpinfo) have their own chapters. This chapter covers the other two settings. Each hook in the `config.json` file is an array of objects, which themselves are essentially `include`/`code` pairs. The `include` value will pull in a given C header file, if it hasn't been already, so that the `code` will have access to its contents. The `code` value is the logic run by the hook itself, and while you can technically put any valid C in here, it is **_strongly_** recommended to put logic longer than one or two lines into a separate C source file (such as the one pulled in along with your `include`d header file), and use a single-line function call here. diff --git a/en/optimizers.md b/en/optimizers.md index 3f43c1ec0..b491b0a69 100644 --- a/en/optimizers.md +++ b/en/optimizers.md @@ -175,7 +175,7 @@ double my_calculate_pi(zval *accuracy) { } ``` -This file must be added at a special section in the [config.json](/[[language]]/[[version]]/config) file: +This file must be added at a special section in the [config.json](/{{ page.version }}/{{ page.language }}/config) file: ```json "extra-sources": [ diff --git a/es-ES/config.md b/es-ES/config.md index 1453edeea..c3a0d52c5 100644 --- a/es-ES/config.md +++ b/es-ES/config.md @@ -187,7 +187,7 @@ Extension description - any text describing your extension: ## destructores -This setting lets you provide one or more C functions to be executed on certain extension lifecycle events - specifically, `RSHUTDOWN` (`request`), `PRSHUTDOWN` (`post-request`), `MSHUTDOWN` (`module`), and `GSHUTDOWN` (`globals`). Check the [lifecycle hooks](/[[language]]/[[version]]/lifecycle) chapter for more information. +This setting lets you provide one or more C functions to be executed on certain extension lifecycle events - specifically, `RSHUTDOWN` (`request`), `PRSHUTDOWN` (`post-request`), `MSHUTDOWN` (`module`), and `GSHUTDOWN` (`globals`). Check the [lifecycle hooks](/{{ page.version }}/{{ page.language }}/lifecycle) chapter for more information. { "destructors": [ @@ -321,7 +321,7 @@ Any additional files you want to add to the compilation process - the search dir ## globals -Extension globals available. Check the [globals](/[[language]]/[[version]]/globals) chapter for more information. +Extension globals available. Check the [globals](/{{ page.version }}/{{ page.language }}/globals) chapter for more information. { "globals": { @@ -341,7 +341,7 @@ Extension globals available. Check the [globals](/[[language]]/[[version]]/globa ## info -`phpinfo()` sections. Check the [phpinfo()](/[[language]]/[[version]]/phpinfo) chapter for more information. +`phpinfo()` sections. Check the [phpinfo()](/{{ page.version }}/{{ page.language }}/phpinfo) chapter for more information. { "info": [ @@ -360,7 +360,7 @@ Extension globals available. Check the [globals](/[[language]]/[[version]]/globa ## iniciadores -This setting lets you provide one or more C functions to be executed on certain extension lifecycle events - specifically, `GINIT` (`globals`), `MINIT` (`module`), and `RINIT` (`request`). Check the [lifecycle hooks](/[[language]]/[[version]]/lifecycle) chapter for more information. +This setting lets you provide one or more C functions to be executed on certain extension lifecycle events - specifically, `GINIT` (`globals`), `MINIT` (`module`), and `RINIT` (`request`). Check the [lifecycle hooks](/{{ page.version }}/{{ page.language }}/lifecycle) chapter for more information. { "initializers": [ @@ -549,4 +549,4 @@ Compiler warnings which should be enabled or disabled in the current project: "nonexistent-function": true, "nonexistent-class": true } - } \ No newline at end of file + } diff --git a/es-ES/lifecycle.md b/es-ES/lifecycle.md index 0eec388e5..27e06c3d3 100644 --- a/es-ES/lifecycle.md +++ b/es-ES/lifecycle.md @@ -18,7 +18,7 @@ Consider the following diagram: ![The PHP Process/Request Lifecycle](/assets/content/lifecycle.png) -Lifecycle hooks are registered in the `config.json` file. As you can see in the diagram above, there are four types of lifecycle hooks - `globals`, `initializers`, `destructors`, and `info`. Each of these has its own corresponding root-level setting in the configuration, and both [globals](/[[language]]/[[version]]/globals) and [info](/[[language]]/[[version]]/phpinfo) have their own chapters. This chapter covers the other two settings. +Lifecycle hooks are registered in the `config.json` file. As you can see in the diagram above, there are four types of lifecycle hooks - `globals`, `initializers`, `destructors`, and `info`. Each of these has its own corresponding root-level setting in the configuration, and both [globals](/{{ page.version }}/{{ page.language }}/globals) and [info](/{{ page.version }}/{{ page.language }}/phpinfo) have their own chapters. This chapter covers the other two settings. Each hook in the `config.json` file is an array of objects, which themselves are essentially `include`/`code` pairs. The `include` value will pull in a given C header file, if it hasn't been already, so that the `code` will have access to its contents. The `code` value is the logic run by the hook itself, and while you can technically put any valid C in here, it is ***strongly*** recommended to put logic longer than one or two lines into a separate C source file (such as the one pulled in along with your `include`d header file), and use a single-line function call here. @@ -103,4 +103,4 @@ The `destructors` block looks something like this: } ``` -Much as the `initializers` block is responsible for defining hooks into the Init events shown in the diagram above, *this* block is responsible for defining hooks into the Shutdown events. There are four of these: `request` for finalizing any data before a response is sent to the client, `post-request` for cleaning up after a response has been sent, `module` for cleaning up after the extension itself before the PHP process shuts down, and `globals` for cleaning up the global variable space. \ No newline at end of file +Much as the `initializers` block is responsible for defining hooks into the Init events shown in the diagram above, *this* block is responsible for defining hooks into the Shutdown events. There are four of these: `request` for finalizing any data before a response is sent to the client, `post-request` for cleaning up after a response has been sent, `module` for cleaning up after the extension itself before the PHP process shuts down, and `globals` for cleaning up the global variable space. diff --git a/es-ES/optimizers.md b/es-ES/optimizers.md index 269a6bf03..0712651e6 100644 --- a/es-ES/optimizers.md +++ b/es-ES/optimizers.md @@ -171,7 +171,7 @@ This file must contain the Zend Engine headers, and the C implementation of the } -This file must be added at a special section in the [config.json](/[[language]]/[[version]]/config) file: +This file must be added at a special section in the [config.json](/{{ page.version }}/{{ page.language }}/config) file: "extra-sources": [ "utils/pi.c" @@ -185,4 +185,4 @@ Lastly you will have to specify where Zephir can find your optimizer by using th ] -Check the complete source code of this example [here](https://github.com/phalcon/zephir-samples/tree/master/ext-optimizers) \ No newline at end of file +Check the complete source code of this example [here](https://github.com/phalcon/zephir-samples/tree/master/ext-optimizers) diff --git a/es-ES/tutorial.md b/es-ES/tutorial.md index 205de3995..abb4e351e 100644 --- a/es-ES/tutorial.md +++ b/es-ES/tutorial.md @@ -75,7 +75,7 @@ Si todo está bien, debería ver la siguiente ayuda (o algo muy similar): -W([a-z0-9\-]+) Apaga una advertencia -Si algo salió mal, por favor regrese a la [página de instalación](/[[language]]/[[version]]/installation). +Si algo salió mal, por favor regrese a la [página de instalación](/{{ page.version }}/{{ page.language }}/installation). @@ -274,4 +274,4 @@ En el siguiente video tutorial puedes ver como crear la extensión explicada en ## Conclusión -Este es un tutorial muy simple y como se puede ver, es fácil empezar a construir una extensión usando Zephir. Te invitamos a seguir leyendo el manual para que puedas descubrir algunas funciones adicionales que ofrece Zephir! \ No newline at end of file +Este es un tutorial muy simple y como se puede ver, es fácil empezar a construir una extensión usando Zephir. Te invitamos a seguir leyendo el manual para que puedas descubrir algunas funciones adicionales que ofrece Zephir! diff --git a/ru-RU/config.md b/ru-RU/config.md index e61a35d2d..2f1dcc7f9 100644 --- a/ru-RU/config.md +++ b/ru-RU/config.md @@ -187,7 +187,7 @@ Extension description - any text describing your extension: ## destructors -This setting lets you provide one or more C functions to be executed on certain extension lifecycle events - specifically, `RSHUTDOWN` (`request`), `PRSHUTDOWN` (`post-request`), `MSHUTDOWN` (`module`), and `GSHUTDOWN` (`globals`). Check the [lifecycle hooks](/[[language]]/[[version]]/lifecycle) chapter for more information. +This setting lets you provide one or more C functions to be executed on certain extension lifecycle events - specifically, `RSHUTDOWN` (`request`), `PRSHUTDOWN` (`post-request`), `MSHUTDOWN` (`module`), and `GSHUTDOWN` (`globals`). Check the [lifecycle hooks](/{{ page.version }}/{{ page.language }}/lifecycle) chapter for more information. { "destructors": [ @@ -321,7 +321,7 @@ Any additional files you want to add to the compilation process - the search dir ## globals -Extension globals available. Check the [globals](/[[language]]/[[version]]/globals) chapter for more information. +Extension globals available. Check the [globals](/{{ page.version }}/{{ page.language }}/globals) chapter for more information. { "globals": { @@ -341,7 +341,7 @@ Extension globals available. Check the [globals](/[[language]]/[[version]]/globa ## info -`phpinfo()` sections. Check the [phpinfo()](/[[language]]/[[version]]/phpinfo) chapter for more information. +`phpinfo()` sections. Check the [phpinfo()](/{{ page.version }}/{{ page.language }}/phpinfo) chapter for more information. { "info": [ @@ -360,7 +360,7 @@ Extension globals available. Check the [globals](/[[language]]/[[version]]/globa ## initializers -This setting lets you provide one or more C functions to be executed on certain extension lifecycle events - specifically, `GINIT` (`globals`), `MINIT` (`module`), and `RINIT` (`request`). Check the [lifecycle hooks](/[[language]]/[[version]]/lifecycle) chapter for more information. +This setting lets you provide one or more C functions to be executed on certain extension lifecycle events - specifically, `GINIT` (`globals`), `MINIT` (`module`), and `RINIT` (`request`). Check the [lifecycle hooks](/{{ page.version }}/{{ page.language }}/lifecycle) chapter for more information. { "initializers": [ @@ -549,4 +549,4 @@ Compiler warnings which should be enabled or disabled in the current project: "nonexistent-function": true, "nonexistent-class": true } - } \ No newline at end of file + } diff --git a/ru-RU/lifecycle.md b/ru-RU/lifecycle.md index 9b095b5e0..5e5e9d631 100644 --- a/ru-RU/lifecycle.md +++ b/ru-RU/lifecycle.md @@ -18,7 +18,7 @@ Consider the following diagram: ![The PHP Process/Request Lifecycle](/assets/content/lifecycle.png) -Lifecycle hooks are registered in the `config.json` file. As you can see in the diagram above, there are four types of lifecycle hooks - `globals`, `initializers`, `destructors`, and `info`. Each of these has its own corresponding root-level setting in the configuration, and both [globals](/[[language]]/[[version]]/globals) and [info](/[[language]]/[[version]]/phpinfo) have their own chapters. This chapter covers the other two settings. +Lifecycle hooks are registered in the `config.json` file. As you can see in the diagram above, there are four types of lifecycle hooks - `globals`, `initializers`, `destructors`, and `info`. Each of these has its own corresponding root-level setting in the configuration, and both [globals](/{{ page.version }}/{{ page.language }}/globals) and [info](/{{ page.version }}/{{ page.language }}/phpinfo) have their own chapters. This chapter covers the other two settings. Each hook in the `config.json` file is an array of objects, which themselves are essentially `include`/`code` pairs. The `include` value will pull in a given C header file, if it hasn't been already, so that the `code` will have access to its contents. The `code` value is the logic run by the hook itself, and while you can technically put any valid C in here, it is ***strongly*** recommended to put logic longer than one or two lines into a separate C source file (such as the one pulled in along with your `include`d header file), and use a single-line function call here. @@ -103,4 +103,4 @@ The `destructors` block looks something like this: } ``` -Much as the `initializers` block is responsible for defining hooks into the Init events shown in the diagram above, *this* block is responsible for defining hooks into the Shutdown events. There are four of these: `request` for finalizing any data before a response is sent to the client, `post-request` for cleaning up after a response has been sent, `module` for cleaning up after the extension itself before the PHP process shuts down, and `globals` for cleaning up the global variable space. \ No newline at end of file +Much as the `initializers` block is responsible for defining hooks into the Init events shown in the diagram above, *this* block is responsible for defining hooks into the Shutdown events. There are four of these: `request` for finalizing any data before a response is sent to the client, `post-request` for cleaning up after a response has been sent, `module` for cleaning up after the extension itself before the PHP process shuts down, and `globals` for cleaning up the global variable space. diff --git a/ru-RU/optimizers.md b/ru-RU/optimizers.md index 037a8d907..368fa0eb8 100644 --- a/ru-RU/optimizers.md +++ b/ru-RU/optimizers.md @@ -171,7 +171,7 @@ This file must contain the Zend Engine headers, and the C implementation of the } -This file must be added at a special section in the [config.json](/[[language]]/[[version]]/config) file: +This file must be added at a special section in the [config.json](/{{ page.version }}/{{ page.language }}/config) file: "extra-sources": [ "utils/pi.c" @@ -185,4 +185,4 @@ Lastly you will have to specify where Zephir can find your optimizer by using th ] -Check the complete source code of this example [here](https://github.com/phalcon/zephir-samples/tree/master/ext-optimizers) \ No newline at end of file +Check the complete source code of this example [here](https://github.com/phalcon/zephir-samples/tree/master/ext-optimizers) diff --git a/ru-RU/tutorial.md b/ru-RU/tutorial.md index 8e291841b..e885df07b 100644 --- a/ru-RU/tutorial.md +++ b/ru-RU/tutorial.md @@ -75,7 +75,7 @@ zephir help -W([a-z0-9\-]+) Turns a warning off -Если что-то пошло не так, вернитесь к разделу [установка](/[[language]]/[[version]]/installation). +Если что-то пошло не так, вернитесь к разделу [установка](/{{ page.version }}/{{ page.language }}/installation). @@ -275,4 +275,4 @@ echo $f->alpha("!he#02l3'121lo."); // выведет "hello" ## Заключение -Это очень простой учебник, и, как вы можете видеть, легко начать создание расширений с помощью Zephir. Мы приглашаем вас продолжить чтение руководства, чтобы вы могли ознакомиться с дополнительными функциями, которые предлагает Zephir! \ No newline at end of file +Это очень простой учебник, и, как вы можете видеть, легко начать создание расширений с помощью Zephir. Мы приглашаем вас продолжить чтение руководства, чтобы вы могли ознакомиться с дополнительными функциями, которые предлагает Zephir! diff --git a/uk-UA/config.md b/uk-UA/config.md index 219383f83..65abe9328 100644 --- a/uk-UA/config.md +++ b/uk-UA/config.md @@ -187,7 +187,7 @@ Extension description - any text describing your extension: ## destructors -This setting lets you provide one or more C functions to be executed on certain extension lifecycle events - specifically, `RSHUTDOWN` (`request`), `PRSHUTDOWN` (`post-request`), `MSHUTDOWN` (`module`), and `GSHUTDOWN` (`globals`). Check the [lifecycle hooks](/[[language]]/[[version]]/lifecycle) chapter for more information. +This setting lets you provide one or more C functions to be executed on certain extension lifecycle events - specifically, `RSHUTDOWN` (`request`), `PRSHUTDOWN` (`post-request`), `MSHUTDOWN` (`module`), and `GSHUTDOWN` (`globals`). Check the [lifecycle hooks](/{{ page.version }}/{{ page.language }}/lifecycle) chapter for more information. { "destructors": [ @@ -321,7 +321,7 @@ Any additional files you want to add to the compilation process - the search dir ## globals -Extension globals available. Check the [globals](/[[language]]/[[version]]/globals) chapter for more information. +Extension globals available. Check the [globals](/{{ page.version }}/{{ page.language }}/globals) chapter for more information. { "globals": { @@ -341,7 +341,7 @@ Extension globals available. Check the [globals](/[[language]]/[[version]]/globa ## info -`phpinfo()` sections. Check the [phpinfo()](/[[language]]/[[version]]/phpinfo) chapter for more information. +`phpinfo()` sections. Check the [phpinfo()](/{{ page.version }}/{{ page.language }}/phpinfo) chapter for more information. { "info": [ @@ -360,7 +360,7 @@ Extension globals available. Check the [globals](/[[language]]/[[version]]/globa ## initializers -This setting lets you provide one or more C functions to be executed on certain extension lifecycle events - specifically, `GINIT` (`globals`), `MINIT` (`module`), and `RINIT` (`request`). Check the [lifecycle hooks](/[[language]]/[[version]]/lifecycle) chapter for more information. +This setting lets you provide one or more C functions to be executed on certain extension lifecycle events - specifically, `GINIT` (`globals`), `MINIT` (`module`), and `RINIT` (`request`). Check the [lifecycle hooks](/{{ page.version }}/{{ page.language }}/lifecycle) chapter for more information. { "initializers": [ @@ -549,4 +549,4 @@ Compiler warnings which should be enabled or disabled in the current project: "nonexistent-function": true, "nonexistent-class": true } - } \ No newline at end of file + } diff --git a/uk-UA/lifecycle.md b/uk-UA/lifecycle.md index f29c946b9..eb79c8718 100644 --- a/uk-UA/lifecycle.md +++ b/uk-UA/lifecycle.md @@ -18,7 +18,7 @@ Consider the following diagram: ![The PHP Process/Request Lifecycle](/assets/content/lifecycle.png) -Lifecycle hooks are registered in the `config.json` file. As you can see in the diagram above, there are four types of lifecycle hooks - `globals`, `initializers`, `destructors`, and `info`. Each of these has its own corresponding root-level setting in the configuration, and both [globals](/[[language]]/[[version]]/globals) and [info](/[[language]]/[[version]]/phpinfo) have their own chapters. This chapter covers the other two settings. +Lifecycle hooks are registered in the `config.json` file. As you can see in the diagram above, there are four types of lifecycle hooks - `globals`, `initializers`, `destructors`, and `info`. Each of these has its own corresponding root-level setting in the configuration, and both [globals](/{{ page.version }}/{{ page.language }}/globals) and [info](/{{ page.version }}/{{ page.language }}/phpinfo) have their own chapters. This chapter covers the other two settings. Each hook in the `config.json` file is an array of objects, which themselves are essentially `include`/`code` pairs. The `include` value will pull in a given C header file, if it hasn't been already, so that the `code` will have access to its contents. The `code` value is the logic run by the hook itself, and while you can technically put any valid C in here, it is ***strongly*** recommended to put logic longer than one or two lines into a separate C source file (such as the one pulled in along with your `include`d header file), and use a single-line function call here. @@ -103,4 +103,4 @@ The `destructors` block looks something like this: } ``` -Much as the `initializers` block is responsible for defining hooks into the Init events shown in the diagram above, *this* block is responsible for defining hooks into the Shutdown events. There are four of these: `request` for finalizing any data before a response is sent to the client, `post-request` for cleaning up after a response has been sent, `module` for cleaning up after the extension itself before the PHP process shuts down, and `globals` for cleaning up the global variable space. \ No newline at end of file +Much as the `initializers` block is responsible for defining hooks into the Init events shown in the diagram above, *this* block is responsible for defining hooks into the Shutdown events. There are four of these: `request` for finalizing any data before a response is sent to the client, `post-request` for cleaning up after a response has been sent, `module` for cleaning up after the extension itself before the PHP process shuts down, and `globals` for cleaning up the global variable space. diff --git a/uk-UA/optimizers.md b/uk-UA/optimizers.md index ca8211eca..9f9ee469b 100644 --- a/uk-UA/optimizers.md +++ b/uk-UA/optimizers.md @@ -171,7 +171,7 @@ This file must contain the Zend Engine headers, and the C implementation of the } -This file must be added at a special section in the [config.json](/[[language]]/[[version]]/config) file: +This file must be added at a special section in the [config.json](/{{ page.version }}/{{ page.language }}/config) file: "extra-sources": [ "utils/pi.c" @@ -185,4 +185,4 @@ Lastly you will have to specify where Zephir can find your optimizer by using th ] -Check the complete source code of this example [here](https://github.com/phalcon/zephir-samples/tree/master/ext-optimizers) \ No newline at end of file +Check the complete source code of this example [here](https://github.com/phalcon/zephir-samples/tree/master/ext-optimizers) diff --git a/uk-UA/tutorial.md b/uk-UA/tutorial.md index 26dd94bd4..98bdc71e1 100644 --- a/uk-UA/tutorial.md +++ b/uk-UA/tutorial.md @@ -75,7 +75,7 @@ If everything is well, you should see the following help (or something very simi -W([a-z0-9\-]+) Turns a warning off -If something went wrong, please return back to the [installation](/[[language]]/[[version]]/installation) page. +If something went wrong, please return back to the [installation](/{{ page.version }}/{{ page.language }}/installation) page. @@ -275,4 +275,4 @@ In the following screencast you can watch how to create the extension explained ## Conclusion -This is a very simple tutorial, and as you can see, it's easy to start building extensions using Zephir. We invite you to continue reading the manual so that you can discover additional features offered by Zephir! \ No newline at end of file +This is a very simple tutorial, and as you can see, it's easy to start building extensions using Zephir. We invite you to continue reading the manual so that you can discover additional features offered by Zephir! diff --git a/zh-CN/config.md b/zh-CN/config.md index baa983a12..bdbe37954 100644 --- a/zh-CN/config.md +++ b/zh-CN/config.md @@ -187,7 +187,7 @@ menu: ## destructors -此设置允许您提供一个或多个C函数在某些扩展生命周期事件上执行——具体来说，`RSHUTDOWN`(`请求`)，`PRSHUTDOWN` (`post请求`)，`MSHUTDOWN` (<0 >0 module1)， <0 >2 GSHUTDOWN3 (<0 >4 globals5)。 查看[lifecycle hooks](/[[language]]/[[version]]/lifecycle)章节了解更多信息。 +此设置允许您提供一个或多个C函数在某些扩展生命周期事件上执行——具体来说，`RSHUTDOWN`(`请求`)，`PRSHUTDOWN` (`post请求`)，`MSHUTDOWN` (<0 >0 module1)， <0 >2 GSHUTDOWN3 (<0 >4 globals5)。 查看[lifecycle hooks](/{{ page.version }}/{{ page.language }}/lifecycle)章节了解更多信息。 { "destructors": [ @@ -321,7 +321,7 @@ menu: ## globals -扩展全局可用。 查看[globals](/[[language]]/[[version]]/globals)章节了解更多信息。 +扩展全局可用。 查看[globals](/{{ page.version }}/{{ page.language }}/globals)章节了解更多信息。 { "globals": { @@ -341,7 +341,7 @@ menu: ## info -`phpinfo()` 信息. 查看[phpinfo()](/[[language]]/[[version]]/phpinfo)章节了解更多信息。 +`phpinfo()` 信息. 查看[phpinfo()](/{{ page.version }}/{{ page.language }}/phpinfo)章节了解更多信息。 { "info": [ @@ -360,7 +360,7 @@ menu: ## initializers -这个设置允许您提供一个或多个C函数在某些扩展生命周期事件上执行——具体来说，`GINIT` (`globals`)， `MINIT` (`module`)， `RINIT` (<0 >0 request1)。 查看[lifecycle hooks](/[[language]]/[[version]]/lifecycle)章节了解更多信息。 +这个设置允许您提供一个或多个C函数在某些扩展生命周期事件上执行——具体来说，`GINIT` (`globals`)， `MINIT` (`module`)， `RINIT` (<0 >0 request1)。 查看[lifecycle hooks](/{{ page.version }}/{{ page.language }}/lifecycle)章节了解更多信息。 { "initializers": [ @@ -549,4 +549,4 @@ menu: "nonexistent-function": true, "nonexistent-class": true } - } \ No newline at end of file + } diff --git a/zh-CN/lifecycle.md b/zh-CN/lifecycle.md index 562228632..b4f0c8453 100644 --- a/zh-CN/lifecycle.md +++ b/zh-CN/lifecycle.md @@ -18,7 +18,7 @@ PHP提供了几个生命周期事件，这些扩展可以用来执行常见的 ![PHP进程/请求生命周期](/assets/content/lifecycle.png) -生命周期钩子注册在`config.json`。 如上图所示，有四种生命周期钩子 — `globals`， `initializers`，`destructors`，`info`。 每一个都在配置中有自己对应的根级别设置，[globals](/[[language]]/[[version]]/globals)和[info](/[[language]]/[[version]]/phpinfo)都有自己的章节。 本章将介绍另外两种设置。 +生命周期钩子注册在`config.json`。 如上图所示，有四种生命周期钩子 — `globals`， `initializers`，`destructors`，`info`。 每一个都在配置中有自己对应的根级别设置，[globals](/{{ page.version }}/{{ page.language }}/globals)和[info](/{{ page.version }}/{{ page.language }}/phpinfo)都有自己的章节。 本章将介绍另外两种设置。 每个钩子在`config.json`文件是一个对象数组，其本身本质上是`include`/`code`对。 `include`值，如果还没有，则会拉入一个给定的C头文件，这样`code`就可以访问它的内容。 `code`值是由钩的逻辑本身, 虽然在技术上你可以把任何有效的C, 它是*** 强烈***建议把逻辑超过一个或两个行到一个单独的C源文件(比如一个拉连同你的`include` d头文件), 并使用一个单行的函数调用。 @@ -103,4 +103,4 @@ PHP提供了几个生命周期事件，这些扩展可以用来执行常见的 } ``` -正如 `initializers` 块负责定义上图中显示的 init 事件中的挂钩一样, *this* 块负责定义关机事件中的挂钩。 有四个:`request`响应之前敲定任何数据发送到客户端,`post-request`清理响应被发送后,`module模块扩展后的清理本身PHP进程关闭之前, 和globals`清理全局变量空间。 \ No newline at end of file +正如 `initializers` 块负责定义上图中显示的 init 事件中的挂钩一样, *this* 块负责定义关机事件中的挂钩。 有四个:`request`响应之前敲定任何数据发送到客户端,`post-request`清理响应被发送后,`module模块扩展后的清理本身PHP进程关闭之前, 和globals`清理全局变量空间。 diff --git a/zh-CN/optimizers.md b/zh-CN/optimizers.md index 61902006c..da133028f 100644 --- a/zh-CN/optimizers.md +++ b/zh-CN/optimizers.md @@ -171,7 +171,7 @@ Zephir 的一个好做法是创建不修改其参数的函数。 如果要更改 } -这个文件必须在[config.json ](/[[language]]/[[version]]/config)中的一个特殊部分中添加: +这个文件必须在[config.json ](/{{ page.version }}/{{ page.language }}/config)中的一个特殊部分中添加: "extra-sources": [ "utils/pi.c" @@ -185,4 +185,4 @@ Zephir 的一个好做法是创建不修改其参数的函数。 如果要更改 ] -检查此示例的完整源代码 [here](https://github.com/phalcon/zephir-samples/tree/master/ext-optimizers) \ No newline at end of file +检查此示例的完整源代码 [here](https://github.com/phalcon/zephir-samples/tree/master/ext-optimizers) diff --git a/zh-CN/tutorial.md b/zh-CN/tutorial.md index a43c51172..4262e5bab 100644 --- a/zh-CN/tutorial.md +++ b/zh-CN/tutorial.md @@ -75,7 +75,7 @@ zephir 帮助 -W([a-z0-9\-]+) Turns a warning off -如果出现问题, 请返回到 [installation](/[[language]]/[[version]]/installation) 页面。 +如果出现问题, 请返回到 [installation](/{{ page.version }}/{{ page.language }}/installation) 页面。 @@ -275,4 +275,4 @@ echo $f->alpha("!he#02l3'121lo."); // prints "hello" ## 结语 -这是一个非常简单的教程, 正如您所看到的, 使用 Zephir开始构建扩展很容易。 我们邀请您继续阅读手册, 以便您可以发现 Zephir提供的其他功能! \ No newline at end of file +这是一个非常简单的教程, 正如您所看到的, 使用 Zephir开始构建扩展很容易。 我们邀请您继续阅读手册, 以便您可以发现 Zephir提供的其他功能!