From 2a97d343306cb851fd3a6417a91e1a968f6f83f9 Mon Sep 17 00:00:00 2001 From: Dustin Wilson Date: Tue, 10 Jan 2023 23:39:16 -0600 Subject: [PATCH] Minor edits to README --- README.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index b8a05b8..26ee812 100644 --- a/README.md +++ b/README.md @@ -62,7 +62,7 @@ Catcher comes built-in with the following handlers: ### A Note About Warnings & Notices ### -As described in the summary paragraph at the beginning of this document, Catcher by default converts all warnings, notices, etc. to `Throwable`s and then proceeds to throw them. Normally, when throwing that halts execution no matter what, but with Catcher that is not the case. +As described in the summary paragraph at the beginning of this document, Catcher by default converts all warnings, notices, etc. to `Throwable`s and then proceeds to throw them. Normally, when throwing that halts execution no matter what, but with Catcher that is not always the case. ```php $catcher = new Catcher(); @@ -79,7 +79,7 @@ Output: Ook! ``` -This is accomplished internally because of [`pcntl_fork`][d]. The throw is done in a separate fork which causes that fork to exit after the `Throwable` is handled while the main process is allowed to continue. `pcntl_fork` is a POSIX function and therefore is only available for use in CLI UNIX environments; this means that it will work neither in Windows nor in Web environments. We also understand this might be undesirable behavior to some, so turning this off is as simple as setting `Catcher::$forking` to false. +This is accomplished internally because of [`pcntl_fork`][d]. The throw is done in a separate fork which causes that fork to exit after the `Throwable` is handled while the main process is allowed to continue. `pcntl_fork` is a POSIX function and therefore is only available for use in CLI UNIX environments; this means that it will work neither in Windows nor in Web environments. We also understand this might be undesirable behavior to many, so turning this off is as simple as setting `Catcher::$forking` to false. ## Documentation @@ -113,7 +113,7 @@ class Catcher { #### Properties -_forking_: When set to true Catcher will throw converted notices, warnings, etc. in a fork, allowing for execution to continue afterwards +_forking_: When set to true Catcher will throw converted notices, warnings, etc. in a fork, allowing for execution to continue afterwards _preventExit_: When set to true Catcher won't exit at all even after fatal errors or exceptions _throwErrors_: When set to true Catcher will convert errors to throwables